Skip to main content
CVE-2026-128021VulnerabilityPublished

FrankenPHP before 1.13.2 contains an information disclosure vulnerability that allows later clients to read earlier

Source GCVE Database

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

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

Data as of 13 Nov 2026, 13:47 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.2
CVSS:4.0/AV:N/AC:H/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 13 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 13 Nov 2026.

What to do

Upgrade frankenphp to 1.13.2.

Affected software

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

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.2 or later, where this issue is fixed by resetting the LIBXML error list between requests. Since this is a software vulnerability with a fixed version, applying the official patch is the recommended remediation.

Description

FrankenPHP versions prior to 1.13.2 have an information disclosure vulnerability where libxml errors from earlier client requests are not cleared before processing later requests. This allows attackers sending requests to the same worker thread to access libxml error information from other clients, potentially revealing parsed document fragments and server filesystem paths.

References

Community reviews

Loading reviews…