CVE-2026-94642

waiting for further signalsZero needs more public information before it can validate it.

GHSA-q2f2-ff6q-g7p9 ↗EUVD-2026-91408 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Apache Software Foundation Apache Thrift < 0.25.0
fixed in 0.25.0
CWE-248 Uncaught Exception
ETK-2026-479, permanent identifier
18d 01h 36msince last run
2h 02mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+33h12m
0
+2h
+4h
+6h
+8h
+10h

description

Apache Thrift PHP bindings before 0.25.0 are affected by an uncaught-exception flaw. An attacker may trigger an exception that terminates a PHP Thrift server process when an affected PHP service processes the relevant input.

mitigation

Upgrade Apache Thrift to version 0.25.0. Prioritize PHP services using the affected bindings, especially TSimpleServer deployments.

fixed in 0.25.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.43%35th percentile
agent run time
2h 02m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 10:57Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-02 10:57Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-94642

{
  "etk_id": "ETK-2026-479",
  "cve_id": "CVE-2026-94642",
  "display_id": "CVE-2026-94642",
  "ghsa_id": "GHSA-q2f2-ff6q-g7p9",
  "euvd_id": "EUVD-2026-91408",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Uncaught exception handling in Apache Thrift PHP bindings",
  "summary": "Apache Thrift PHP bindings before 0.25.0 are affected by an uncaught-exception flaw. An attacker may trigger an exception that terminates a PHP Thrift server process when an affected PHP service processes the relevant input.",
  "mitigation": "Upgrade Apache Thrift to version 0.25.0. Prioritize PHP services using the affected bindings, especially TSimpleServer deployments.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Thrift",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.25.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.25.0"
      ],
      "package_name": "apache/thrift",
      "purl": null
    }
  ],
  "cwes": [
    248
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0043,
  "epss_percentile": 0.3573,
  "epss_asof": "2026-10-21",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 121.67656975,
  "t0_at": "2026-10-02T10:57:14.927000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T10:57:14.927000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T10:57:14.927000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-94642"
    }
  }
}

published 2026-10-03 18:07Z
last change 2026-10-21 20:26Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.