PHP denial of service in HTTP stream wrapper header parsing
Affects PHP 8.1.32 to 8.1.34 and earlier 8.2 to 8.5 builds when code fetches HTTP or HTTPS URLs via stream functions. Fixed in 8.2.36, 8.3.37, 8.4.28 and 8.5.13; no 8.1 fix is listed.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.2.36, 8.3.37, 8.4.28, 8.5.13
- Who is exposed
- Not reported
Summary
PHP, the PHP Group's scripting language, has a denial-of-service flaw in how its HTTP stream wrapper parses folded response headers. An attacker who controls an HTTP or HTTPS response that PHP fetches, such as one from a URL the application requests or a server it already contacts, can remotely and without logging in make PHP workers consume excessive CPU time, and repeated or concurrent requests can cause a denial of service.
Written by a model
Original description
Denial of service through folded HTTP response headers.
The HTTP stream wrapper joins each continuation line of a folded response header to the accumulated value by allocating a new string and copying the whole value, so a response with many short continuation lines takes disproportionate CPU time to parse. An attacker who controls an HTTP or HTTPS response fetched through file_get_contents(), fopen() or other stream functions, by making the application request a chosen URL or by influencing a server it already contacts, can keep PHP workers busy. Repeated or concurrent requests can cause a denial of service.
This issue affects PHP versions from 8.1.32 through 8.1.34, from 8.2.28 before 8.2.36, from 8.3.18 before 8.3.37, from 8.4.5 before 8.4.28 and 8.5.* before 8.5.13.
Who should check
Teams running PHP 8.1.32-8.1.34, 8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28 or 8.5 before 8.5.13 that fetch HTTP or HTTPS URLs with file_get_contents() or fopen(), including WordPress or Drupal hosts.
Not fixed by: Request timeouts do not remove the vulnerable parsing behaviour.
“The affected code was introduced by the fix for GHSA-v8xr-gpvj-cx9g , first released in PHP 8.1.32, 8.2.28, 8.3.19 and 8.4.5.”
What to do
Upgrade to a fixed version: 8.2.36, 8.3.37, 8.4.28, 8.5.13.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-127960 (Denial of service through folded HTTP response headers), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-127960 (entry last updated 2026-11-19):
Affected:
- PHP Group PHP: from 8.1.32, through 8.1.34; from 8.2.28, fixed in 8.2.36; from 8.3.18, fixed in 8.3.37; from 8.4.5, fixed in 8.4.28; from 8.5.0, fixed in 8.5.13
Fixed versions: 8.2.36, 8.3.37, 8.4.28, 8.5.13.
Conditions (all must be true for the bug to be hit):
- PHP 8.1.32 through 8.1.34, 8.2.28 before 8.2.36, 8.3.18 before 8.3.37, 8.4.5 before 8.4.28, or 8.5.x before 8.5.13 (the affected code was introduced by the GHSA-v8xr-gpvj-cx9g fix). (source: https://github.com/php/php-src/security/advisories/GHSA-mmf9-xm3v-hg2x)
- The application fetches an HTTP or HTTPS URL through PHP's stream functions such as file_get_contents() or fopen(). (source: https://github.com/php/php-src/security/advisories/GHSA-mmf9-xm3v-hg2x)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-127960 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127960 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/php/php-src/security/advisories/GHSA-mmf9-xm3v-hg2x
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-127960
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127960"}.Affected versions
- PHP Group PHPFrom 8.1.32 · through 8.1.34; From 8.2.28 · fixed in 8.2.36; From 8.3.18 · fixed in 8.3.37; From 8.4.5 · fixed in 8.4.28; From 8.5.0 · fixed in 8.5.13
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach17/20Affects PHP (a widely deployed server, runtime, framework or database)
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 91 if added to CISA KEV
- Would score about 86 if CISA's SSVC rates exploitation active
- Would score about 51 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · php/php-src · Advisory GHSA-mmf9-xm3v-hg2x |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-127960 |
| Record | NVD · CVE-2026-127960 |
Questions about CVE-2026-127960
Is CVE-2026-127960 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Folded HTTP response headers can make PHP use excessive CPU while fetching an HTTP or HTTPS URL through stream functions. The slowdown can keep PHP workers busy and block other requests.
Source: github.com
Which versions are affected by CVE-2026-127960?
PHP: from 8.1.32 through 8.1.34; from 8.2.28 before 8.2.36; from 8.3.18 before 8.3.37; from 8.4.5 before 8.4.28; from 8.5.0 before 8.5.13.
Source: cve.now feed data
Am I affected, and how do I check?
Affected are PHP 8.1.32 through 8.1.34, 8.2.28 before 8.2.36, 8.3.18 before 8.3.37, 8.4.5 before 8.4.28, and 8.5.x before 8.5.13. Check the version with php -v, and look for code that calls file_get_contents() or fopen() on HTTP or HTTPS URLs.
Source: github.com
How do I fix CVE-2026-127960?
Upgrade to PHP 8.2.36, 8.3.37, 8.4.28, or 8.5.13 or later in the matching branch. The facts list no fixed 8.1 release and no vendor patch identifiers.
Source: github.com
Related
- CVE-2026-129289PHP-FPM request smuggling through an unread HTTP request body
- CVE-2026-129496Timezone cache use-after-free can lead to remote code execution
- CVE-2026-129481Use-after-free after interrupted session shutdown
- CVE-2026-126714Partially overwritten session files can lead to remote code execution
- CVE-2026-129474Use-after-free in magic method backtraces can lead to remote code execution
- CVE-2026-115560Session serializer mismatch can lead to remote code execution
No corrections so far. Something wrong on this page? Report an error.