dbcve.org
Traffic ServerApplication · Apache

CVE-2025-58136

HIGH · 7.5 CVSS v3.1 Published 2026-04-02
Fix available
A fix is available. Upgrade to 9.2.13 / 10.1.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
A bug in POST request handling causes a crash under a certain condition. This issue affects Apache Traffic Server: from 10.0.0 through 10.1.1, from 9.0.0 through 9.2.12. Users are recommended to upgrade to version 10.1.2 or 9.2.13, which fix the issue. A workaround for older versions is to set proxy.config.http.request_buffer_enabled to 0 (the default value is 0).

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 4mo ago

Surfaced from public web coverage — external links open in a new tab.

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 · moderate confidence

Apache Traffic Server contains a denial-of-service vulnerability in its POST request handling logic. When a specific condition is met during POST request processing, the server crashes, leading to service disruption. This affects versions 9.0.0-9.2.12 and 10.0.0-10.1.1.

MitigationUpgrade to Apache Traffic Server 9.2.13 or 10.1.2, or verify that proxy.config.http.request_buffer_enabled remains at its default value of 0 as a workaround.

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:>= 9.0.0, < 9.2.13>= 10.0.0, < 10.1.2

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
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 version via your package manager, then compare against the affected ranges: 9.0.0 to 9.2.12, or 10.0.0 to 10.1.1
    Affected if Installed version falls within either 9.0.0 <= version < 9.2.13 or 10.0.0 <= version < 10.1.2
  2. Inspect request buffer configuration
    Query the configuration value using 'traffic_ctl config get proxy.config.http.request_buffer_enabled' or check records.config for this setting
    Affected if The value is set to 1 (enabled) rather than the default of 0

You are affected if your Apache Traffic Server version is within the vulnerable range AND proxy.config.http.request_buffer_enabled is set to a non-default value, enabling the POST request handling code path that triggers the crash.

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.13 / 10.1.2 or later
Fixed in 9.2.1310.1.2
Interim mitigation

Upgrade to Apache Traffic Server 9.2.13 or 10.1.2, or verify that proxy.config.http.request_buffer_enabled remains at its default value of 0 as a workaround.

Recommended fix High confidence

9.2.13 or 10.1.2

  1. 1. Download Apache Traffic Server version 9.2.13 or 10.1.2 (or later) from the official Apache download source.
  2. 2. Stop the Apache Traffic Server service safely.
  3. 3. Back up the current configuration files and data directories as a precaution.
  4. 4. Install or upgrade to the downloaded fixed version using your system's package manager or build from source.
  5. 5. Restore your configuration files if needed, ensuring proxy.config.http.request_buffer_enabled remains at its default value of 0 (or set it to 0 if not already).
  6. 6. Start the Traffic Server service.
  7. 7. Verify the service is running correctly and test POST request handling to confirm the crash no longer occurs.

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58136 — 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-2025-58136 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