Skip to main content
CVE-2026-122233VulnerabilityPublished

FrankenPHP before 1.13.4 contains an information disclosure vulnerability in worker mode that fails to clear last HTTP

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-122233· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.13.4 when convenient.

Data as of 4 Nov 2026, 22:39 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.3
CNA (VulnCheck)CVSS 3.13.7
Patch
Available – fixed in 1.13.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Upgrade frankenphp to 1.13.4.

Affected software

ProductAffectedFixed in
phpfrankenphpAffected
  • <1.13.4
Fixed in
  • 1.13.4
Gofrankenphppkg:golang/frankenphpOther threatsAffected
  • <1.13.4
Fixed in
  • 1.13.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade FrankenPHP to version 1.13.4 or later, where this issue is fixed. Since the vulnerability is addressed in this version, applying the official patch is the recommended remediation.

Description

FrankenPHP versions before 1.13.4 have an information disclosure vulnerability in worker mode. The vulnerability arises because HTTP stream response headers are not cleared between requests, allowing subsequent requests on the same worker thread to access headers from previous requests. This can expose sensitive headers such as Set-Cookie or tokens from backend APIs to other users.

References

Community reviews

Loading reviews…