CVE
FrankenPHP authentication bypass in header name handling
Affects FrankenPHP before 1.13.0 (1.12.7 and earlier), in Caddy mode or embedded mode, when PHP or an upstream proxy trusts dash-form headers like X-Forwarded-For from $_SERVER. Fixed in 1.13.0.
Written by anthropic/claude-sonnet-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 1.13.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.13.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.46% · 40th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 43/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
FrankenPHP has a flaw that lets a remote attacker, without logging in, send specially named headers (using dots instead of dashes) that PHP rewrites into trusted ones. This lets the attacker spoof headers PHP reads from `$_SERVER`, which can bypass authentication or authorization, fake the client IP to defeat IP-based access control, rate limiting and audit logs, or fake the request scheme to downgrade https to http.
Original description
FrankenPHP before 1.13.0 contains an authentication bypass vulnerability that allows unauthenticated attackers to spoof trusted headers by sending dot-form header names that PHP rewrites to underscores. Attackers can send headers like X.Authenticated.User or X.Forwarded.For that map to $_SERVER keys, spoofing user identity, client IP, or scheme.
Who should check
Teams running FrankenPHP 1.12.7 or earlier (Caddy mode or embedded Go library) whose PHP apps trust headers like X-Forwarded-For or X-Authenticated-User from $_SERVER.
Not fixed by: Upgrading to 1.12.4 with Caddy 2.11.4 does not fix it; that only drops underscore headers, not dot-form ones.
“Affected versions <= 1.12.7 Patched versions 1.13.0”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach17/20Affects PHP (a widely deployed server, runtime, framework or database)
- Severity9.1/10CVSS 9.1
- No patch0/5No signal
What would change the score
- Would score about 88 if added to CISA KEV
- Would score about 83 if CISA's SSVC rates exploitation active
- Would score about 48 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.13.0.
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-128023 (FrankenPHP before 1.13.0 Authentication Bypass via Dot-Form Header Name Aliasing), 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-128023 (entry last updated 2026-11-13):
Affected:
- php frankenphp: fixed in 1.13.0
Fixed versions: 1.13.0.
Conditions (all must be true for the bug to be hit):
- FrankenPHP version 1.12.7 or earlier (fixed in 1.13.0), in Caddy server mode or as the standalone Go library / embedded mode (source: https://github.com/php/frankenphp/security/advisories/GHSA-qcrp-8483-f2f2)
- The PHP application or an upstream proxy trusts a dash-form request header (such as X-Forwarded-For or X-Authenticated-User) read from $_SERVER (source: https://github.com/php/frankenphp/security/advisories/GHSA-qcrp-8483-f2f2)
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-128023 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128023 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/frankenphp/security/advisories/GHSA-qcrp-8483-f2f2
- https://www.vulncheck.com/advisories/frankenphp-before-1.13.0-authentication-bypass-via-dot-form-header-name-aliasing
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-128023
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-128023"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- php frankenphp
fixed in 1.13.0
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-128023
Is CVE-2026-128023 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?
A remote client can send a header name written in a dot form that FrankenPHP maps onto a dash-form header such as X-Forwarded-For or X-Authenticated-User in $_SERVER. This lets the client spoof trusted headers, which can bypass authentication or authorization, fake the client IP, or fake the request scheme (https to http downgrade).Source: github.com
Which versions are affected by CVE-2026-128023?
frankenphp: before 1.13.0.Source: cve.now feed data
Am I affected, and how do I check?
FrankenPHP versions before 1.13.0 (1.12.7 and earlier) are listed, in both Caddy server mode and the standalone Go library or embedded mode. The issue matters where the PHP application or an upstream proxy trusts a dash-form request header read from $_SERVER. To check, look at the installed FrankenPHP version and whether the application relies on such headers.Source: github.com
How do I fix CVE-2026-128023?
Upgrade FrankenPHP to 1.13.0 or later. The facts name no workaround.Source: github.com