Skip to content

CVE-2026-109619

Use After Free: Is CVE-2026-109619 real, exploitable, or a false positive? Here's the community verdict.

Community verdict: No field verdicts yet. Be the first practitioner to weigh in.

signals

public sources

Exploited in wild
Yes
CISA KEV · Oct 26, 2026
Public exploit
PoC (unverified)
Metasploit/EDB/PoC
Base severity
8.1 High
CVSS
Exploitation prob.
100%
FIRST EPSS
Weakness
CWE-416 · Use After Free
CWE

Confirmed exploited in the wild. Patch this first, regardless of the base score.

cisa ssvc

CISA Vulnrichment · assessed

Exploitation
Active
in the wild
Automatable
No
at scale
Technical impact
Total
on success

CISA decision, by how critical the affected system is to you:

  • low impact → Track
  • medium impact → Attend
  • high impact → Act

Track: normal patch cycle · Track*: watch closely · Attend: patch sooner · Act: patch now. About SSVC ↗

public exploits

links to sources — we don’t host code

Unverified proof-of-concept code has been published. It may or may not be functional — assess before relying on it.

baseline read

auto · not a community verdict

Real — exploited in the wild

CISA confirms active exploitation. Treat scanner hits as true positives unless your specific version or config is unaffected.

Based on CISA KEV

Confirm or dispute →

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

PHP has various global state that temporarily points into request memory. In some scenarios, global state may not be correctly reset, or may be repopulated after being reset. The global state may then refer to request memory even after it has been freed. Subsequent requests may read or branch on this stale state before it is fully initialized. Multiple strategies can trigger this condition and produce remote code execution (RCE).

Published · Added to CISA KEV (5 days after publication)

Embed this verdict
TruePositive verdict for CVE-2026-109619
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2026-109619/badge.svg)](https://www.truepositive.app/cve/CVE-2026-109619)
HTML
<a href="https://www.truepositive.app/cve/CVE-2026-109619"><img src="https://www.truepositive.app/cve/CVE-2026-109619/badge.svg" alt="TruePositive verdict for CVE-2026-109619"></a>

Live badge that updates automatically as the community verdict changes.

timeline

  1. CISA SSVC exploitation changed · none → active
  2. Public exploit recorded · 5 sources
  3. CISA SSVC assessment · exploitation: active
  4. Added to CISA KEV · confirmed exploited in the wild
  5. Published by NVD
  6. Added to VulnCheck KEV · reported exploited in the wild

Score and exploit changes tracked since .

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: TruePositive's read from public sources is Real & exploitable — a starting point, not a community verdict.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    PHP Stale Internal Request-State Vulnerability — PHP contains a stale internal request-state vulnerability that allows for unauthenticated remote code execution. Listed in the CISA KEV catalog (added 2026-10-26) — confirmed exploited in the wild, not theoretical. FIRST EPSS puts the chance of exploitation in the next 30 days at ~100%. Treat it as real and prioritize remediation over triage.

  • 0
    Remediation · TruePositive EditorialCurated

    Required action for PHP Group PHP: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. CISA set a federal remediation due date of 2026-10-29. After patching, verify the vulnerable path is no longer reachable before closing the finding.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.

Same weakness: CWE-416 · Use After Free.