CVE-2026-65325: Apache Traffic Server: HTTP/2 multiplexed origin sessions are reused without certificate re-verification

Published Jul 29, 2026
·
Updated

Apache Traffic Server reuses multiplexed HTTP/2 origin connections without verifying the server certificate covers the new request hostname.

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 fix the issue.

Affected Software

3 affected components
Apache Traffic Server>=9.0.0<=9.2.14, >=10.0.0<=10.1.3
Apache Traffic Server>=9.0.0<9.2.15
Apache Traffic Server>=10.0.0<10.1.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apache Traffic Server to a version that resolves this vulnerability.

    Fixed in 9.2.15
  2. Upgrade

    Upgrade Apache Traffic Server to a version that resolves this vulnerability.

    Fixed in 10.1.4

Event History

Jul 29, 2026
CVE Published
via MITRE·08:23 AM
Data Sourced
via MITRE·08:23 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-65325?

The severity of CVE-2026-65325 is medium, with a score of 4.8.

2

How do I fix CVE-2026-65325?

To fix CVE-2026-65325, upgrade Apache Traffic Server to version 9.2.15 or 10.1.4.

3

What impact does CVE-2026-65325 have on Apache Traffic Server?

CVE-2026-65325 allows for the reuse of multiplexed HTTP/2 origin connections without proper server certificate verification, posing a security risk.

4

Which versions of Apache Traffic Server are affected by CVE-2026-65325?

Apache Traffic Server versions from 9.0.0 through 9.2.14 and from 10.0.0 through 10.1.3 are affected by CVE-2026-65325.

5

Is CVE-2026-65325 remotely exploitable?

Yes, CVE-2026-65325 has an attack vector that is classified as remote.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203