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

Back
New CVE Detected

CVE-2026-58162 – SNI-Based Certificate Forgery / Man-in-the-Middle – Apache Traffic Server 8.0.0–…

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-58162 is a critical (CVSS 10.0) improper certificate validation vulnerability (CWE-295) in the Apache Traffic Server certifier plugin, affecting versions 8.0.0 through 10.1.3. The plugin dynamically generates SSL/TLS certificates on demand using the client-supplied Server Name Indication (SNI) value from the TLS ClientHello message — a value that is entirely attacker-controlled — enabling an unauthenticated remote attacker to trigger certificate generation for arbitrary domain names and conduct man-in-the-middle (MitM) attacks against clients served by the proxy. Patches are available in Apache Traffic Server 9.2.15 and 10.1.4.

Technical details

  • Root cause: The certifier plugin does not validate or restrict the SNI value supplied by the client before using it to generate an SSL/TLS certificate. This falls under CWE-295 (Improper Certificate Validation): the plugin trusts fully attacker-controlled input to make certificate issuance decisions.
  • Trigger conditions: Exploitation requires the certifier plugin to be active. The plugin is optional and not enabled by default, but is commonly deployed in SSL bump and TLS interception configurations — a standard pattern in enterprise reverse-proxy and CDN environments.
  • Attack vector: An unauthenticated remote attacker sends a crafted TLS ClientHello message containing a manipulated SNI value over the network. No user interaction and no prior privileges are required.
  • Impact: By controlling the SNI value, an attacker can cause ATS to generate and serve a forged certificate for any domain name of their choosing, enabling interception and manipulation of TLS traffic for arbitrary domains. The CVSS Scope is Changed (S:C), meaning the impact extends beyond ATS itself to downstream clients that trust certificates issued by the proxy’s root CA. Integrity impact is HIGH and Availability impact is HIGH.

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: 10.0 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H

Mitigation and recommended actions

  • Immediate patch: Upgrade to Apache Traffic Server 9.2.15 or 10.1.4, which contain the vendor-provided fix per the Apache Software Foundation advisory.
  • If immediate patching is not possible: Disable the certifier plugin entirely if SSL bump / TLS interception is not operationally required. Restricting inbound TLS connections at the network perimeter can reduce exposure but should not be treated as a substitute for patching.

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