Skip to main content
VulnerabilityPublished

CVE-2026-24033: Apache Traffic Server · HTTP Request/Response Smuggling

Affects Apache Traffic ServerSource CVE Database V5

0

Not known to be exploited · CVSS 7.2 High.

Data as of 28 Oct 2026, 05:11 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Apache Software FoundationApache Traffic ServerAffected
  • >=10.0.0 <=10.1.3
  • >=9.0.0 <=9.2.14
Fixed in–

AI-suggested

Users should upgrade affected Apache Traffic Server instances to versions 9.2.15 or 10.1.4, which contain the official fixes for this vulnerability. No other mitigation or temporary workaround is indicated. Patch status is confirmed by the vendor's version recommendations.

Description

CVE-2026-24033 is a high-severity vulnerability in Apache Traffic Server involving inconsistent interpretation of HTTP requests, also known as HTTP Request/Response Smuggling. This affects versions from 9.0.0 through 9.2.14 and 10.0.0 through 10.1.3. The vulnerability can lead to partial confidentiality and integrity impacts but does not affect availability. Users are advised to upgrade to versions 9.2.15 or 10.1.4 where the issue is fixed.

References

Community reviews

Loading reviews…