CVE-2026-45062
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFrankenPHP is a modern application server for PHP. From version 1.11.2 to before version 1.12.3, the splitPos() function in cgi.go misuses golang.org/x/text/search with search.IgnoreCase when the request path contains a non-ASCII byte. Two distinct flaws in that fallback let an attacker mislead FrankenPHP into treating a non-.php file as a .php script. In any deployment where the attacker can place content into a file served by FrankenPHP (uploads, file storage, etc.), this can be escalated to remote code execution by crafting a URL whose path triggers either flaw. This issue has been patched in version 1.12.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceFrankenPHP versions 1.11.2 through 1.12.2 have a flaw in the splitPos() function in cgi.go that incorrectly handles non-ASCII bytes in request paths when using golang.org/x/text/search with search.IgnoreCase. This causes non-.php files to be misidentified as PHP scripts, enabling RCE when an attacker can place malicious content in files served by FrankenPHP (e.g., uploads, file storage).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify FrankenPHP versionRun 'frankenphp --version' or check the binary metadata to determine the installed version numberAffected if Version is 1.11.2, 1.11.3, 1.11.4, 1.12.0, 1.12.1, or 1.12.2 (versions 1.11.2 through 1.12.2 are affected)
-
Verify CGI module configurationInspect the FrankenPHP configuration file or running config for any 'cgi' or 'php' directive settings that enable PHP processingAffected if CGI/PHP processing is enabled and the server is configured to handle PHP file requests
-
Check for served user-writable directoriesReview web server configuration to identify directories that FrankenPHP serves where untrusted users can upload or write files (e.g., /uploads, /storage, /userfiles)Affected if Any directory served by FrankenPHP is writable by users or accepts file uploads
-
Inspect access logs for PHP misidentificationReview web server or FrankenPHP access logs for requests to non-.php files that were processed as PHP scripts (look for .jpg, .png, .txt, .html files triggering PHP interpreters)Affected if Logs show non-.php files being executed or processed as PHP scripts
The environment is affected if FrankenPHP version is between 1.11.2 and 1.12.2 inclusive, CGI/PHP processing is enabled, and the server serves any directory where users can upload or write files that could be interpreted as PHP.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade FrankenPHP to version 1.12.3 or later. Additionally, restrict or validate file uploads/storage in directories served by FrankenPHP to prevent attackers from placing executable content.
1.12.3
- Upgrade FrankenPHP to version 1.12.3 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45062 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data