Inappropriate Encoding for Output Context Affecting zipkin package, versions <3.6.1-r40


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.28% (21st 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-22400831
  • published10 Nov 2026
  • disclosed29 Oct 2026

Introduced: 29 Oct 2026

NewCVE-2026-119281  (opens in a new tab)
CWE-838  (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, the connector assumed result bytes were UTF-8 but guarded only changes to character_set_client. It did not reject non-UTF-8 character_set_results changes and relied on the server's global session_track_system_variables configuration to report character-set changes. A malicious or compromised server, or a machine-in-the-middle attacker, could suppress tracking or change the result charset so application strings differed from the returned bytes, potentially defeating application-side validation or escaping that depended on the decoded values. This issue is fixed in versions 3.3.7, 3.4.5, and 3.5.11.

CVSS Base Scores

version 3.1