dbcve.org
FrankenphpApplication · PHP

CVE-2026-24895

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-12
Fix available
A fix is available. Upgrade to 1.11.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
FrankenPHP is a modern application server for PHP. Prior to 1.11.2, FrankenPHP’s CGI path splitting logic improperly handles Unicode characters during case conversion. The logic computes the split index (for finding .php) on a lowercased copy of the request path but applies that byte index to the original path. Because strings.ToLower() in Go can increase the byte length of certain UTF-8 characters (e.g., Ⱥ expands when lowercased), the computed index may not align with the correct position in the original string. This results in an incorrect SCRIPT_NAME and SCRIPT_FILENAME, potentially causing FrankenPHP to execute a file other than the one intended by the URI. This vulnerability is fixed in 1.11.2.

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 confidence

FrankenPHP's CGI path splitting logic has an off-by-one style vulnerability where it computes a split index on a lowercased copy of the request path but applies that byte index to the original path. Since Go's strings.ToLower() can expand the byte length of certain UTF-8 characters (e.g., Ⱥ becomes Ⱥ), the computed index misaligns with the original string, resulting in incorrect SCRIPT_NAME and SCRIPT_FILENAME values that cause execution of an unintended file.

MitigationUpgrade FrankenPHP to version 1.11.2 or later to patch the Unicode case conversion logic flaw.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FrankenphpApplication
Affected:< 1.11.2

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FrankenPHP installation
    Locate the frankenphp binary or running process using commands such as 'which frankenphp', 'ps aux | grep frankenphp', or checking container/runtime inventories
    Affected if FrankenPHP is not found in the environment, then this CVE does not apply
  2. Check installed FrankenPHP version
    Run 'frankenphp --version' or inspect the binary metadata to determine the exact version number
    Affected if The installed version is lower than 1.11.2, indicating the environment contains the vulnerability
  3. Confirm CGI/FastCGI mode is enabled
    Review FrankenPHP configuration files for 'mode: cgi', 'mode: fastcgi', or similar CGI-enabled settings. Check if the server is configured to handle PHP scripts via CGI
    Affected if CGI or FastCGI mode is not enabled, the vulnerable code path may not be exercised
  4. Verify UTF-8 characters in request paths are possible
    Inspect application routing, URL patterns, or any deployed configurations that accept user-controlled path components. Determine if non-ASCII UTF-8 characters could be present in URLs that map to PHP scripts
    Affected if The environment processes paths containing UTF-8 characters that expand when lowercased (such as 'Ⱥ'), enabling the index mismatch to occur

The environment is affected if FrankenPHP version is below 1.11.2, CGI/FastCGI mode is enabled, and the server can receive requests with UTF-8 characters in paths that trigger byte-length changes during lowercasing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.11.2 or later
Fixed in 1.11.2
Vendor patch github.com →
Interim mitigation

Upgrade FrankenPHP to version 1.11.2 or later to patch the Unicode case conversion logic flaw.

Recommended fix High confidence

1.11.2

  1. Check current FrankenPHP version using `frankenphp version` or checking your deployment configuration
  2. Upgrade FrankenPHP to version 1.11.2 or later. If using a package manager, run the equivalent of: `go install github.com/php/[email protected]` or update your container image to a version containing FrankenPHP 1.11.2
  3. Verify the upgrade was successful by running `frankenphp version`
  4. Test your application to confirm CGI path handling works correctly, especially with Unicode characters in URLs
  5. If using Docker, ensure your image is rebuilt with the new FrankenPHP version (e.g., update your Dockerfile to use a base image with FrankenPHP 1.11.2)
Caveat Review the FrankenPHP 1.11.2 release notes for any other changes that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Frankenphp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24895 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24895 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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