dbcve.org
Traffic ServerApplication · Apache

CVE-2026-58162

CRITICAL · 10.0 CVSS v3.1 Published 2026-07-29
Fix available
A fix is available. Upgrade to 9.2.15 / 10.1.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 3 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Apache Traffic Server certifier plugin generates certificates based on attacker-controlled client SNI. This issue affects Apache Traffic Server: from 8.0.0 through 8.1.9, 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Apache Traffic Server certifier plugin has a critical vulnerability (CVSS 10) where it generates TLS certificates based on attacker-controlled Server Name Indication (SNI) values from client connections. This allows remote attackers to obtain certificates for arbitrary domain names, potentially enabling man-in-the-middle attacks and domain impersonation.

MitigationUpgrade Apache Traffic Server to version 9.2.15 or 10.1.4 which contain the fix for this vulnerability. If immediate upgrade is not possible, disable or restrict access to the certifier plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Traffic ServerApplication
Affected:>= 8.0.0, <= 8.1.9>= 9.0.0, < 9.2.15>= 10.0.0, < 10.1.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Traffic Server version
    Run 'traffic_server -V' or check the package manager for the installed version (e.g., 'rpm -q traffic-server' or 'dpkg -l traffic-server')
    Affected if Version is 8.0.0-8.1.9, 9.0.0-9.2.14, or 10.0.0-10.1.3 (vulnerable range)
  2. Locate certifier plugin configuration
    Check the plugin configuration directory (typically /etc/trafficserver/plugin.config or /usr/local/etc/trafficserver/plugin.config) for any 'certifier' or 'cert' entries
    Affected if The certifier plugin is loaded in the configuration
  3. Verify if certifier plugin is enabled
    Review remap.config or records.config for certifier-related settings; also check for any .so plugin files in the plugins directory
    Affected if The certifier plugin is actively enabled in the ATS configuration
  4. Inspect certifier plugin behavior
    If the plugin is enabled, examine its configuration files (typically in /etc/trafficserver/ or within the plugin directory) to see if it accepts SNI input without validation
    Affected if The plugin is configured to generate certificates from client-provided SNI values without ownership validation

You are affected if you are running a vulnerable ATS version (8.0.0-8.1.9, 9.0.0-9.2.14, or 10.0.0-10.1.3) AND the certifier plugin is enabled and processing client SNI requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.2.15 / 10.1.4 or later
Fixed in 9.2.1510.1.4
Interim mitigation

Upgrade Apache Traffic Server to version 9.2.15 or 10.1.4 which contain the fix for this vulnerability. If immediate upgrade is not possible, disable or restrict access to the certifier plugin.

Recommended fix High confidence

9.2.15 or 10.1.4

  1. 1. Identify your current Apache Traffic Server version using 'traffic_server --version' or equivalent
  2. 2. Determine which upgrade path suits your deployment (9.2.15 or 10.1.4) - note version 8.x is not directly patched, so migrate to 9.x or 10.x
  3. 3. Review release notes for your target version for any migration considerations
  4. 4. Back up your current ATS configuration, certificates, and data directories
  5. 5. Stop the Apache Traffic Server service
  6. 6. Install the fixed version (9.2.15 or 10.1.4) using your system's package manager or compile from source
  7. 7. Restore your configuration from backup, verifying compatibility with the new version
  8. 8. Start the Apache Traffic Server service

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Traffic Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58162 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-58162 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data