SNI policy bypass via partial hostname matching
Published Jul 29, 2026 · Updated Jul 29, 2026
Improper access control in Apache Traffic Server 9.0.0 through 9.1.14 and 10.0.0 through 10.1.3 allows remote attackers to bypass SNI policies. SSLSNIConfig compares only a hostname prefix without confirming equal full-string lengths, so a crafted Host value can pass as the TLS SNI name. The bypass requires an inbound TLS route with a relevant sni.yaml verify_client or ip_allow policy and can defeat client-certificate or source-IP restrictions.
Summary
What happened
Improper access control in Apache Traffic Server 9.0.0 through 9.1.14 and 10.0.0 through 10.1.3 allows remote attackers to bypass SNI policies. SSLSNIConfig compares only a hostname prefix without confirming equal full-string lengths, so a crafted Host value can pass as the TLS SNI name. The bypass requires an inbound TLS route with a relevant sni.yaml verify_client or ip_allow policy and can defeat client-certificate or source-IP restrictions.
The record
- CVE
- CVE-2026-41920
- Published
- Jul 29, 2026
- Updated
- Jul 29, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Traffic Server
- Classifications
- CWE-284, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 2026CVE publishedPublication date reported by the CVE source.
- Jul 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.0 <=10.1.3
- Affected versionversion=9.0.0 <=9.1.14
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo