Remote code execution via Unicode path confusion
Published Feb 12, 2026 · Updated Feb 12, 2026
Path confusion in FrankenPHP before 1.11.2 allows remote attackers to execute non-PHP files as PHP through a crafted request path. The splitPos function calculates a byte offset after lowercasing the UTF-8 path, then splitCgiPath applies that offset to the original bytes when setting SCRIPT_NAME and SCRIPT_FILENAME. Exploitation requires an attacker-controlled file in the document root or another reachable path and yields remote code execution under the server process.
Summary
What happened
Path confusion in FrankenPHP before 1.11.2 allows remote attackers to execute non-PHP files as PHP through a crafted request path. The splitPos function calculates a byte offset after lowercasing the UTF-8 path, then splitCgiPath applies that offset to the original bytes when setting SCRIPT_NAME and SCRIPT_FILENAME. Exploitation requires an attacker-controlled file in the document root or another reachable path and yields remote code execution under the server process.
The record
- CVE
- CVE-2026-24895
- Published
- Feb 12, 2026
- Updated
- Feb 12, 2026
- Vendor
- The PHP Group
- Product
- FrankenPHP
- Classifications
- CWE-20, CWE-180, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 12, 2026CVE publishedPublication date reported by the CVE source.
- Feb 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.11.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream Unicode byte-offset proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo