Skip to content

ApplicationsCritical 9.2Patch available

CVE-2026-126714

Partial session-file writes in PHP allow object injection and remote code execution.

How scary is it?

updated 20 Nov 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • Yes

    Proof-of-concept code is public2

    5 GitHub proofs of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list3

    Not in the catalog as of our last sync.

Scare-o-meter

Act this week

Serious and within reach of attackers. Schedule the fix this week.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: Public proof-of-concept code exists for a network-reachable flaw; CVSS 9.2.1 Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run PHP Group PHP in an affected version< 8.2.36 / >= 8.3.0 and < 8.3.37 / >= 8.4.0 and < 8.4.28 (+1 more)

    < 8.2.36 >= 8.3.0 and < 8.3.37 >= 8.4.0 and < 8.4.28 >= 8.5.0 and < 8.5.13

    The CVE record states no fixed release.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

  3. Specific conditions are met that the attacker does not control

    CVSS attack requirements: Present (AT:P). The attack depends on deployment or execution conditions. The CVE record does not always say which.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per our analysisA patch is available

    The CVE record we hold states no fixed release number. See the advisories in the references.

    See the references

  2. Recommendation, AI-writtenUpgrade PHP to the fixed releases, restart services, and audit session handling.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. Affects PHP, a ubiquitous web runtime; unauthenticated RCE in mainstream PHP releases can lead to widespread compromise of web applications and servers.

CVSS
9.2Criticalscored by the publisher (CNA)
Exploited in the wild
Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
EPSS
13.1%chance of exploitation in the next 30 daystop 4% of scored CVEsFIRST score of 21 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
19 Nov 2026analysed here 20 Nov 2026

Summary

Impact

Remote code execution via attacker-controlled session data and interrupted writes that enable object injection and gadget-chain execution.

Triage

Exploitable
At runtime
Attack vector
network
Weaknesses
Can a WAF block it?
Partly. See why

Executive summary (AI-written)

CVE-2026-126714 poses a significant threat to organizations using affected versions of PHP, with a critical CVSS score of 9.2. This vulnerability enables attackers to execute arbitrary code remotely by exploiting weaknesses in session management, specifically through object injection. Given that PHP is a foundational technology for many web applications, the impact of an unauthenticated remote code execution (RCE) could lead to severe security breaches, resulting in data loss, service disruption, and potential legal repercussions for organizations that fail to address it promptly. Immediate action is required to mitigate risks associated with this vulnerability. Affected organizations should prioritize upgrading PHP to the patched versions, which not only addresses this vulnerability but also enhances overall security posture. Failing to act could expose systems to widespread compromise, leading to cascading effects across various business operations and damaging the organization's reputation.

Technical analysis (AI-written)

CVE-2026-126714 is classified with a CVSS score of 9.2, indicating a major vulnerability affecting multiple versions of PHP prior to 8.2.36, and various releases in the 8.3, 8.4, and 8.5 series. This flaw specifically relates to partial session-file writes that can lead to object injection vulnerabilities and enable remote code execution (RCE) under specific conditions. The primary attack vector involves manipulating session data, allowing an attacker to craft malicious serialized objects that can be executed on the server when subsequently deserialized. The complexity of exploiting this vulnerability is moderate. An attacker does not require authenticated access, thereby broadening the attack surface significantly. The interrupted write condition exploited during session handling means that even if one of the session writes is incomplete, an attacker can leverage this to inject their own objects, which can be chained together to execute arbitrary code. As PHP is widely implemented in numerous web applications and frameworks, the potential for damage is extensive, making this an attractive target for malicious actors. Mitigation strategies should focus on immediate upgrading of PHP to the patched versions, specifically 8.2.36, 8.3.37, 8.4.28, and 8.5.13 or later. In addition, organizations should review and enhance their session management practices. Recommendations include implementing strong input validation for session data, regular security audits of session handling code, and employing logging mechanisms to detect anomalous session activity. It is also advisable to conduct a broader security assessment to identify any additional vulnerabilities that may stem from insecure session management. By taking these steps, organizations can significantly reduce their risk exposure stemming from this critical vulnerability and protect their applications against potential exploitation.

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources.

Affected products

ProductAffected versions
PHP Group PHP< 8.2.36>= 8.3.0 and < 8.3.37>= 8.4.0 and < 8.4.28>= 8.5.0 and < 8.5.13Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • PHP < 8.2.36
  • PHP 8.3.x < 8.3.37
  • PHP 8.4.x < 8.4.28
  • PHP 8.5.x < 8.5.13

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? Partly. Cloudflare publishes WAF rules written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.

Also consider: patch · enable the vendor rule in block mode

Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Unvetted proof-of-concept code on GitHub: 5 GitHub proofs of concept
CISA SSVC
exploitation none, automatable yes, technical impact totalAssessed by CISA 19 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 19 Nov 2026CISA SSVC assessment: exploitation none
  2. 19 Nov 2026Published1 day later
  3. 20 Nov 2026First proof-of-concept repository on GitHub (unvetted)same day later
  4. 20 Nov 2026CVE record last updatedsame day later
  5. 20 Nov 2026Analysed by vulneraibility.comsame day later

Common questions

Is CVE-2026-126714 being exploited?

Not confirmed. CVE-2026-126714 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 13% probability of exploitation in the next 30 days.

How severe is CVE-2026-126714?

CVE-2026-126714 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-126714?

Yes. A fix has been recorded for CVE-2026-126714. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-126714 affect?

CVE-2026-126714 affects PHP < 8.2.36, PHP 8.3.x < 8.3.37, PHP 8.4.x < 8.4.28, PHP 8.5.x < 8.5.13. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-126714?

Upgrade PHP to the fixed releases, restart services, and audit session handling.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

5 references in the CVE record, grouped by the tags the record gives them.

Advisories (1)

  • github.com /php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp

Other links (4)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.