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

Back
New CVE Detected

CVE-2026-58182 – Uncontrolled Resource Consumption / Denial of Service – Apache Traffic Server 8….

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-58182 is a high-severity uncontrolled resource consumption vulnerability (CWE-400) in the ts_lua plugin of Apache Traffic Server (ATS), affecting versions 8.0.0 through 10.1.3. The flaw arises from the plugin’s mishandling of initialization, transform context, and per-instance state, and is exploitable remotely without authentication or user interaction. It carries a CVSS v3.1 base score of 8.6 (HIGH), reflecting high availability impact alongside partial confidentiality and integrity risk.

Technical details

  • Root cause: The ts_lua plugin — which embeds a LuaJIT engine inside Apache Traffic Server for scriptable HTTP proxy logic — incorrectly manages initialization sequences, transform context lifecycle, and per-instance state. This mishandling leads to uncontrolled resource consumption (CWE-400), enabling an attacker to exhaust server resources through crafted network requests.
  • Trigger conditions: The ts_lua plugin must be explicitly loaded (via plugin.config for global mode or remap.config for remap mode) — it is not enabled by default. Instances running ATS without the ts_lua plugin active are not affected.
  • Attack vector: Network-reachable; no authentication, privileges, or user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: High availability impact (server resource exhaustion leading to degraded performance or denial of service), with partial confidentiality and integrity compromise reflected in the CVSS v3.1 scoring (C:L/I:L/A:H). No public proof-of-concept exploit has been identified at the time of publication.

Affected software

  • Apache Traffic Server 8.0.0 through 8.1.9
  • Apache Traffic Server 9.0.0 through 9.2.14
  • Apache Traffic Server 10.0.0 through 10.1.3

Severity

CVSS v3.1 Base Score: 8.6 (HIGH)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Mitigation and recommended actions

  • Immediate action — upgrade: Apply the vendor-released fix by upgrading to Apache Traffic Server 9.2.15 (for 9.x branches) or 10.1.4 (for 10.x branches). No fix is available for the 8.x branch; users on 8.x should migrate to a supported release.
  • If immediate patching is not possible: Disable or remove the ts_lua plugin from plugin.config and remap.config to eliminate the attack surface. Network-layer controls limiting untrusted access to ATS instances can reduce exposure but do not constitute a full remediation.

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge