CVE-2026-111804

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

EUVD-2026-107490 ↗

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 Traffic Server >= 10.0.0, <= 10.1.4; 10.2.0
CWE-416 Use After Free
ETK-2026-2349Zero's internal tracking ID, independent of the CVE number., permanent identifier
25msince last run
39mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h54m
0
+4h
+6h
+8h
+10h
+12h

description

Apache Traffic Server 10.0.0 through 10.1.4 and 10.2.0 are affected when the experimental wasm plugin is in use. A network attacker can trigger a transaction-close memory-lifetime flaw and cause untrusted metric identifiers to reach the internal statistics interface.

mitigation

Upgrade Apache Traffic Server to 10.1.5 or 10.2.1. Disable the experimental wasm plugin until the update is deployed.

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.
contextual
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.
–
agent run time
39m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 18:21Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-21 18:21Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2349",
  "cve_id": "CVE-2026-111804",
  "display_id": "CVE-2026-111804",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-107490",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Use-after-free in Apache Traffic Server wasm plugin",
  "summary": "Apache Traffic Server 10.0.0 through 10.1.4 and 10.2.0 are affected when the experimental wasm plugin is in use. A network attacker can trigger a transaction-close memory-lifetime flaw and cause untrusted metric identifiers to reach the internal statistics interface.",
  "mitigation": "Upgrade Apache Traffic Server to 10.1.5 or 10.2.1. Disable the experimental wasm plugin until the update is deployed.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Traffic Server",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.0.0, <= 10.1.4",
        "10.2.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Apache Traffic Server",
      "purl": null
    }
  ],
  "cwes": [
    416
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 38.72448725,
  "t0_at": "2026-10-21T18:21:32.055000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T18:21:32.055000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T18:21:32.055000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111804"
    }
  }
}

published 2026-10-21 19:37Z
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.