CRLF Injection Affecting drupal-10.6 package, versions <10.6.12-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.16% (6th 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-DRUPAL106-17434070
  • published24 Jun 2026
  • disclosed23 Jun 2026

Introduced: 23 Jun 2026

CVE-2026-55766  (opens in a new tab)
CWE-93  (opens in a new tab)
CWE-113  (opens in a new tab)

How to fix?

Upgrade Minimos:latest drupal-10.6 to version 10.6.12-r0 or higher.

NVD Description

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

guzzlehttp/psr7 is a PSR-7 HTTP message library implementation in PHP. Prior to 2.12.1, guzzlehttp/psr7 did not reject CR/LF characters in certain first-party HTTP start-line fields: the request method, protocol version, and response reason phrase. If an application placed attacker-controlled data into one of those fields and later serialized the PSR-7 message as raw HTTP/1.x, for example with Message::toString() or an equivalent serializer, the serialized message could contain attacker-controlled header lines. The issue can also be reached through Message::parseRequest() or Message::parseResponse() when malformed raw messages are parsed into first-party PSR-7 objects and then serialized again. Creating or modifying a Request, Response, or other PSR-7 object alone is not sufficient. The issue requires the malformed message to be serialized and written to the network, forwarded, replayed, or otherwise processed by software that does not independently reject the malformed start line. This vulnerability is fixed in 2.12.1.