Skip to main content
← Vulnerabilities

FrankenPHP before 1.13.4 Cross-Request Response Header Leak in Worker Mode

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 1.13.4
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.13.4.

40Pcve.now Index 40 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Data gap: No advisory context yet
  • Reach17/20Affects PHP (a widely deployed server, runtime, framework or database)
  • Severity6.3/10CVSS 6.3
  • No patch0/5No signal

What would change the score

  • Would score about 85 if added to CISA KEV
  • Would score about 80 if CISA's SSVC rates exploitation active
  • Would score about 45 if advisories confirm default setups are exposed

CVE-2026-122233 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects frankenphp; fixed in 1.13.4.

Published
Last modified
Published
Not listed in CISA KEV
40/100 · provisional
Fix
Fixed in 1.13.4
None on Exploit-DB, Metasploit or GitHub

Summary

FrankenPHP, a PHP application server, is affected in its worker mode, where a request can read HTTP response headers left behind by earlier requests handled on the same worker thread. An attacker can do this remotely, without logging in, and could see sensitive headers such as other users' Set-Cookie or token values from backend APIs.

Read the original description

FrankenPHP before 1.13.4 contains an information disclosure vulnerability in worker mode that fails to clear last HTTP stream response headers between requests, because the reset only happens in RSHUTDOWN, which worker requests skip. Later requests calling http_get_last_response_headers() can read headers fetched by earlier requests on the same worker thread, exposing other users' Set-Cookie or token headers from backend APIs.

What to do

  • Upgrade to a fixed version: 1.13.4.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • php frankenphp

    fixed in 1.13.4

Evidence 4

  1. Advisory
  2. Patch
  3. Repository
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-122233

Is CVE-2026-122233 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

Which versions are affected by CVE-2026-122233?

frankenphp: before 1.13.4.Source: cve.now feed data

How do I fix CVE-2026-122233?

Upgrade to a fixed version: 1.13.4.Source: cve.now feed data