Skip to main content
Menu
CVEs

FrankenPHP authentication bypass in header name handling

Affects FrankenPHP before 1.13.0 (Caddy and embedded modes) when a PHP app or upstream proxy trusts dash-form headers like X-Forwarded-For from $_SERVER. Fixed in 1.13.0.

CVE-2026-128023EUVD-2026-125079GHSA-PRM4-W6G7-PW64GHSA-QCRP-8483-F2F2Published November 13, 2026, updated

9.1CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 1.13.0
Who is exposed
Default setups

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.

Written by a model

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 PHP apps on FrankenPHP 1.12.7 or earlier (Caddy or embedded Go) that trust headers like X-Forwarded-For or X-Authenticated-User from $_SERVER.

Not fixed by: Caddy 2.11.4 bundled in FrankenPHP 1.12.4 only drops underscore headers and does not stop the dot form.

“Affected versions <= 1.12.7 Patched versions 1.13.0”

github.com

What to do

  1. Check every install: default setups are affected.

  2. 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-17):
Affected:
- Go package github.com/dunglas/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 both Caddy server mode and 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: the bug is reachable in a default setup; no special feature or setting is needed.
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:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

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"}.

Affected versions

cve.now Index

64of 100 · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure22/25Default setups, reachable over the network without a login
  • Reach17/20Affects PHP (a widely deployed server, runtime, framework or database)
  • Severity10/10CVSS 9.1, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 89 if added to CISA KEV
  • Would score about 84 if CISA's SSVC rates exploitation active

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now4 days
  4. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  5. Record last updated

Public exploit activity

100%0Posted on X by cve.nowNov 13Nov 22
  • EPSS: 0.46%
  • Posted on X by cve.now Nov 13

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

On X 2

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · php/frankenphp · Advisory GHSA-qcrp-8483-f2f2
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-128023
RecordNVD · CVE-2026-128023
Other links 1
Linkvulncheck.com · advisories/frankenphp-before-1.13.0-authentication-bypass-via-dot-form-header-name-aliasing

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. CISA's SSVC assessment notes a proof of concept exists. 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 dot form that FrankenPHP maps onto a trusted dash-form header in $_SERVER. This lets the client spoof headers the application trusts, such as X-Forwarded-For or X-Authenticated-User, which can bypass authentication or authorization and spoof client IP or request scheme.

Source: github.com

Which versions are affected by CVE-2026-128023?

github.com/dunglas/frankenphp (Go): before 1.13.0.

Source: cve.now feed data

Am I affected, and how do I check?

FrankenPHP 1.12.7 and earlier, back to the first release, are affected, in both Caddy server mode and standalone Go library/embedded mode. It matters when the PHP application or an upstream proxy trusts a dash-form request header read from $_SERVER. Check 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 advisory lists no workaround.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.