Inappropriate Encoding for Output Context Affecting keycloak package, versions <26.7.2-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.34% (28th 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-MINIMOSLATEST-KEYCLOAK-19431160
  • published30 Aug 2026
  • disclosed28 Aug 2026

Introduced: 28 Aug 2026

NewCVE-2026-55858  (opens in a new tab)
CWE-838  (opens in a new tab)

How to fix?

Upgrade Minimos:latest keycloak to version 26.7.2-r0 or higher.

NVD Description

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

MariaDB Connector/J is used to connect applications developed in Java to MariaDB and MySQL databases. Prior to 2.7.14, 3.3.5, 3.4.3, and 3.5.9, the connector encodes and decodes protocol text and performs client-side escaping under the assumption that the connection character set is UTF-8. The server can report a mid-session change to character_set_client through OK-packet session-state tracking, including a change caused by SET NAMES, a stored routine or trigger, server configuration, or a hostile server. If character_set_client changes to a non-UTF-8 value, the driver continues to read and write UTF-8 while the server interprets the same bytes under another encoding, causing silent data corruption and a client/server charset-confusion mismatch that can defeat byte-wise quoting or escaping. The fix accepts only utf8, utf8mb3, or utf8mb4 after initialization; any other value causes SQLException with SQLState 08000 and closes the connection. This issue is fixed in versions 2.7.14, 3.3.5, 3.4.3, and 3.5.9.