CRLF Injection Affecting keycloak-advanced-compat package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (13th 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 Learn

Learn about CRLF Injection vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMOSLATEST-KEYCLOAKADVANCEDCOMPAT-16439179
  • published7 May 2026
  • disclosed6 May 2026

Introduced: 6 May 2026

NewCVE-2026-41417  (opens in a new tab)
CWE-93  (opens in a new tab)
CWE-444  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest keycloak-advanced-compat.

NVD Description

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

Netty allows request-line validation to be bypassed when a DefaultHttpRequest or DefaultFullHttpRequest is created first and its URI is later changed via setUri(). The constructors reject CRLF and whitespace characters that would break the start-line, but setUri() does not apply the same validation. HttpRequestEncoder and RtspEncoder then write the URI into the request line verbatim. If attacker-controlled input reaches setUri(), this enables CRLF injection and insertion of additional HTTP or RTSP requests, leading to HTTP request smuggling or desynchronization on the HTTP side and request injection on the RTSP side. This issue is fixed in versions 4.2.13.Final and 4.1.133.Final.