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

Back
New CVE Detected

CVE-2026-102795 – SNI/Host Header Policy Bypass – Apache Traffic Server 9.0.0–9.2.14 / 10.0.0–10.1.3

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-102795 is an Improper Access Control vulnerability (CWE-284) in Apache Traffic Server affecting enforcement of the SNI-to-Host-header matching policy. The flaw allows the proxy to route a request to a virtual host based on a mismatch between the TLS SNI value and the HTTP Host header, rather than enforcing consistency between the two. The issue carries a Critical CVSS v3.1 score of 9.3 and is remotely exploitable without authentication.

Technical details

  • Root cause: Apache Traffic Server fails to properly enforce its configured policy for matching the SNI value presented during the TLS handshake against the Host header value in the subsequent HTTP request.
  • Trigger conditions: An attacker sends a TLS connection with one SNI value and an HTTP request with a differing Host header to a Traffic Server instance that routes/terminates TLS for multiple virtual hosts or back-end origins.
  • Attack vector: Network-based, no authentication or user interaction required, low attack complexity.
  • Impact: The server may resolve the request against the wrong virtual host context, potentially allowing an attacker to access or influence content/configuration associated with a different hostname served by the same proxy. Per the CVSS vector, this results in low confidentiality impact and high integrity impact, with a changed security scope (availability is not affected).

Affected software

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

Mitigation and recommended actions

  • Immediate: Upgrade to Apache Traffic Server 9.2.15 or 10.1.4, which fix this issue.
  • If immediate patching is not possible: Review and explicitly configure the proxy.config.http.host_sni_policy setting (or the per-mapping host_sni_policy directive in sni.yaml) to ENFORCED so that requests with mismatched SNI and Host header values are rejected, and restrict exposure of multi-tenant TLS termination endpoints until the upgrade is applied.

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