Improper Handling of Length Parameter Inconsistency Affecting zipkin package, versions <3.6.1-r40


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.35% (29th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-ZIPKIN-22400833
  • published10 Nov 2026
  • disclosed29 Oct 2026

Introduced: 29 Oct 2026

NewCVE-2026-119276  (opens in a new tab)
CWE-130  (opens in a new tab)
CWE-789  (opens in a new tab)

How to fix?

Upgrade Chainguard zipkin to version 3.6.1-r40 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream zipkin package and not the zipkin package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. From 3.0.0 until 3.3.7, 3.4.5, and 3.5.11, when CLIENT_SESSION_TRACK was negotiated, the OkPacket.parse() and OkPacket.parseWithInfo() paths allocated byte arrays using server-declared lengths for the OK packet info field and session-state variable names and values before confirming that the bytes remained in the packet. A malicious or compromised server, or a machine-in-the-middle attacker, could send a small OK packet declaring a much larger length and repeatedly force attacker-controlled heap allocations before the subsequent copy failed. This could create garbage-collection pressure or an OutOfMemoryError in the client application. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.

CVSS Base Scores

version 3.1