Skip to content
VulniPulse
Advisory severityHigh8.2Apache Software Foundation Updated

High [CVE-2021-32564 +1] Apache Traffic Server can crash with a null pointer dereference when a client POST request is torn down via half-close while a chunked origin response is being reparsed from a reentrant write-ready callback, a timing-dependent race introduced by the CVE-2021-32564 flow-control backports

This high-severity Apache Software Foundation advisory covers CVE-2026-112381 and CVE-2021-32564 affecting Apache Traffic Server.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations. This bulletin covers 2 CVEs; its score, affected versions and guidance may apply to different issues within that bulletin.

CVE-2026-112381 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Apache Software FoundationInfra & Gateways
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Apache Traffic Server can crash with a null pointer dereference when a client POST request is torn down via half-close while a chunked origin response is being reparsed from a reentrant write-ready callback, a timing-dependent race introduced by the CVE-2021-32564 flow-control backports.

This issue affects Apache Traffic Server: 9.2.15, 10.1.4, 10.2.0.

Users are recommended to upgrade to version 9.2.16, 10.1.5, or 10.2.1, which fix the issue.

Affected versions
  • 9.2.15
  • 10.1.4
  • 10.2.0

Official advisory · high-confidence parse· fetched 11 hours ago·verify at source

Fixed versions
  • 9.2.16
  • 10.1.5
  • 10.2.1

Official advisory · high-confidence parse· fetched 11 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Users are recommended to upgrade to version 9.2.16, 10.1.5, or 10.2.1, which fix the issue.

Official advisory · high-confidence parse· fetched 11 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.