Bug 2491769 (CVE-2026-55766) - CVE-2026-55766 guzzlehttp/psr7: guzzlehttp/psr7: Information disclosure due to improper handling of CR/LF characters in HTTP start-line fields
Summary: CVE-2026-55766 guzzlehttp/psr7: guzzlehttp/psr7: Information disclosure due t...
Keywords:
Status: NEW
Alias: CVE-2026-55766
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2491782 2491783 2491784 2491781 2491785
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-23 16:01 UTC by OSIDB Bzimport
Modified: 2026-06-23 16:16 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-06-23 16:01:29 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.