CVE-2026-24895 Vulnerability Analysis & Exploit Details

CVE-2026-24895
Vulnerability Scoring

9.8
/10
Critical Risk

As a catastrophic security flaw, CVE-2026-24895 has severe implications, demanding immediate intervention.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-24895 Details

Status: Analyzed

Last updated: 🕡 20 Feb 2026, 18:30 UTC
Originally published on: 🕗 12 Feb 2026, 20:16 UTC

Time between publication and last update: 7 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVE-2026-24895 Vulnerability Summary

CVE-2026-24895: 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.

Assessing the Risk of CVE-2026-24895

Access Complexity Graph

The exploitability of CVE-2026-24895 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-24895

With low attack complexity and no required privileges, CVE-2026-24895 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-24895, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-24895, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-24895 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2026-24895 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2026-24895 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-24895 References

External References

CWE Common Weakness Enumeration

CWE-180

CAPEC Common Attack Pattern Enumeration and Classification

  • Leverage Alternate Encoding CAPEC-267 An adversary leverages the possibility to encode potentially harmful input or content used by applications such that the applications are ineffective at validating this encoding standard.
  • Using Leading 'Ghost' Character Sequences to Bypass Input Filters CAPEC-3 Some APIs will strip certain leading characters from a string of parameters. An adversary can intentionally introduce leading "ghost" characters (extra characters that don't affect the validity of the request at the API layer) that enable the input to pass the filters and therefore process the adversary's input. This occurs when the targeted API will accept input data in several syntactic forms and interpret it in the equivalent semantic way, while the filter does not take into account the full spectrum of the syntactic forms acceptable to the targeted API.
  • Using Unicode Encoding to Bypass Validation Logic CAPEC-71 An attacker may provide a Unicode string to a system component that is not Unicode aware and use that to circumvent the filter or cause the classifying mechanism to fail to properly understanding the request. That may allow the attacker to slip malicious data past the content filter and/or possibly cause the application to route the request incorrectly.
  • Using Escaped Slashes in Alternate Encoding CAPEC-78 This attack targets the use of the backslash in alternate encoding. An adversary can provide a backslash as a leading character and causes a parser to believe that the next character is special. This is called an escape. By using that trick, the adversary tries to exploit alternate ways to encode the same character which leads to filter problems and opens avenues to attack.
  • Using Slashes in Alternate Encoding CAPEC-79 This attack targets the encoding of the Slash characters. An adversary would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the adversary many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
  • Using UTF-8 Encoding to Bypass Validation Logic CAPEC-80 This attack is a specific variation on leveraging alternate encodings to bypass validation logic. This attack leverages the possibility to encode potentially harmful input in UTF-8 and submit it to applications not expecting or effective at validating this encoding standard making input filtering difficult. UTF-8 (8-bit UCS/Unicode Transformation Format) is a variable-length character encoding for Unicode. Legal UTF-8 characters are one to four bytes long. However, early version of the UTF-8 specification got some entries wrong (in some cases it permitted overlong characters). UTF-8 encoders are supposed to use the "shortest possible" encoding, but naive decoders may accept encodings that are longer than necessary. According to the RFC 3629, a particularly subtle form of this attack can be carried out against a parser which performs security-critical validity checks against the UTF-8 encoded form of its input, but interprets certain illegal octet sequences as characters.

Vulnerable Configurations

  • cpe:2.3:a:php:frankenphp:1.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.0.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.0.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.0.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.0.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.0.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.0.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.0.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.0.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.0.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.0.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.1.5:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.1.5:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.3.4:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.3.5:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.3.5:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.3.6:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.3.6:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.10.1:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.10.1:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.11.0:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:php:frankenphp:1.11.1:*:*:*:*:*:*:*
    cpe:2.3:a:php:frankenphp:1.11.1:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-24895: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-29023 – Keygraph Shannon contains a hard-coded API key in its router configuration that, when the router component is enabled and exposed, allows network a...
  • CVE-2025-70039 – An issue pertaining to CWE-78: Improper Neutralization of Special Elements used in an OS Command was discovered in linagora Twake v2023.Q1.1223.
  • CVE-2025-70038 – An issue pertaining to CWE-79: Improper Neutralization of Input During Web Page Generation was discovered in linagora Twake v2023.Q1.1223. This all...
  • CVE-2025-70034 – An issue pertaining to CWE-1333: Inefficient Regular Expression Complexity (4.19) was discovered in mscdex ssh2 v1.17.0.
  • CVE-2025-70033 – An issue pertaining to CWE-79: Improper Neutralization of Input During Web Page Generation was discovered in Sunbird-Ed SunbirdEd-portal v1.13.4.