# CVE-2026-102795: Apache Traffic Server: SNI to Host header matching policy is not properly enforced

> Attackers can bypass SNI to Host header matching policies in Apache Traffic Server, potentially circumventing access controls.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-102795, GHSA-r73v-c3ch-65gj, OESA-2026-4231, OESA-2026-4232, OESA-2026-4233, UBUNTU-CVE-2026-102795

## What is CVE-2026-102795?

CVE-2026-102795 is a high-severity missing authorization vulnerability in Apache Traffic Server, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Access Control vulnerability in Apache Traffic Server.

This issue affects Apache Traffic Server: from 9.0.0 through 9.2.14, from 10.0.0 through 10.1.3.

Users are recommended to upgrade to version 9.2.15 or 10.1.4, which fixes the issue.

This CVE supersedes CVE-2026-41920, whose record listed the affected 9.x versions as 9.0.0 through 9.1.14 and the fixed version as 9.1.15. All 9.2.x releases before 9.2.15 are affected.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-102795?


## How do I fix CVE-2026-102795?

Upgrade to a fixed version.

## Is CVE-2026-102795 being exploited?

There is no known exploitation of CVE-2026-102795 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102795 and fix it if it is affected.

What it is: CVE-2026-102795 is a high-severity missing authorization vulnerability in Apache Traffic Server, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102795 in the wild and no public exploit code.

Affected product: Apache Traffic Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102795/ (Markdown: https://insights.sbomify.com/CVE-2026-102795/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102795
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102795
- OSV: https://osv.dev/vulnerability/CVE-2026-102795

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102795/
Summaries are generated and may contain mistakes; the official description above is the record.