CVE-2026-111816
waiting for further signalsZero needs more public information before it can validate it.description
Apache Traffic Server deployments running 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, or 10.2.0 are affected. An attacker who can cause Traffic Server to process a malformed chunked 302 response from an upstream peer may induce inconsistent response parsing, leading to cache poisoning or response desynchronization.
mitigation
Upgrade to Traffic Server 9.2.16, 10.1.5, or 10.2.1, as appropriate for the deployed branch. Migrate affected 8.x deployments to a supported fixed branch, since no 8.x fixed release is listed.
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.
- 2026-10-21 18:26Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-111816
{ "etk_id": "ETK-2026-2350", "cve_id": "CVE-2026-111816", "display_id": "CVE-2026-111816", "ghsa_id": null, "euvd_id": "EUVD-2026-107493", "status": "published", "anchor_state": "anchored", "title": "HTTP response desynchronization in Apache Traffic Server", "summary": "Apache Traffic Server deployments running 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, or 10.2.0 are affected. An attacker who can cause Traffic Server to process a malformed chunked 302 response from an upstream peer may induce inconsistent response parsing, leading to cache poisoning or response desynchronization.", "mitigation": "Upgrade to Traffic Server 9.2.16, 10.1.5, or 10.2.1, as appropriate for the deployed branch. Migrate affected 8.x deployments to a supported fixed branch, since no 8.x fixed release is listed.", "vendor": "Apache Software Foundation", "product": "Apache Traffic Server", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 8.0.0, <= 8.1.11", ">= 9.0.0, <= 9.2.15", ">= 10.0.0, <= 10.1.4", "10.2.0" ], "ecosystem": null, "fixed_versions": [], "package_name": "Apache Traffic Server", "purl": null } ], "cwes": [ 444 ], "cvss_score": 9.2, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:L/SI:H/SA:N", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 33.5077448, "t0_at": "2026-10-21T18:26:32.566000+00:00", "signals": { "trigger_signal": { "at": "2026-10-21T18:26:32.566000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-21T18:26:32.566000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-111816" } } }
published 2026-10-21 20:00Z
last change 2026-10-21 20:58Z
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.