Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-58153 – HTTP Response Smuggling – Apache Traffic Server 10.0.0 through 10.1.3

Be the first to know when new zero-days emerge:

Summary

CVE-2026-58153 is an HTTP response smuggling vulnerability (CWE-444) in Apache Traffic Server (ATS), affecting versions 10.0.0 through 10.1.3. During HTTP/2-to-HTTP/1 protocol conversion, ATS incorrectly forwards HTTP/2 origin trailers to downstream HTTP/1 clients without applying proper chunked transfer-encoding framing. The vulnerability carries a CVSS v3.1 score of 8.3 (High) and is exploitable remotely without authentication or user interaction. The IONIX research team is tracking this vulnerability and recommends immediate patching for all exposed ATS instances.

Technical details

  • Root cause: CWE-444 — Inconsistent Interpretation of HTTP Requests (‘HTTP Request/Response Smuggling’). ATS fails to correctly reframe HTTP/2 trailers into valid chunked-encoding boundaries when performing HTTP/2-to-HTTP/1 protocol downconversion, causing downstream HTTP/1 clients to receive malformed or ambiguous response framing.
  • Trigger conditions: An attacker sends HTTP/2 requests containing origin trailers through an ATS reverse proxy or caching proxy; the unframed trailers are propagated to HTTP/1 clients behind the proxy, enabling response interpretation discrepancies.
  • Attack vector: Network-accessible (AV:N), low complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N).
  • Impact: Scope:Changed (S:C) — the impact extends beyond the ATS process itself to downstream clients and cached content. Partial confidentiality, integrity, and availability impact (C:L/I:L/A:L), consistent with response smuggling or cache poisoning enabling content injection, session hijacking, or cache corruption against clients served by the affected proxy.

Affected software

  • Apache Traffic Server 10.0.0 through 10.1.3

Severity

  • CVSS v3.1 Base Score: 8.3 (High)
  • Vector string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

Mitigation and recommended actions

  • Immediate — patch: Upgrade to Apache Traffic Server 9.2.15 or 10.1.4, as recommended by the Apache Software Foundation in their security advisory.
  • If immediate patching is not feasible, consider restricting network access to ATS instances and monitoring for anomalous HTTP/2 traffic containing unusual trailer fields as a temporary defensive measure.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge