Process memory starvation via unreleased LZMA state
Published Jul 23, 2025 · Updated Jul 23, 2025
Memory leak in LibHTP 0.5.50 and earlier allows remote attackers to starve a parsing process of memory through crafted HTTP traffic. The LZMA error path in htp_decompressors.c marks compression complete without freeing the initialized decoder state. Exploitation requires LZMA decompression to remain enabled; repeated triggering exhausts process memory and removes HTTP inspection visibility.
Summary
What happened
Memory leak in LibHTP 0.5.50 and earlier allows remote attackers to starve a parsing process of memory through crafted HTTP traffic. The LZMA error path in htp_decompressors.c marks compression complete without freeing the initialized decoder state. Exploitation requires LZMA decompression to remain enabled; repeated triggering exhausts process memory and removes HTTP inspection visibility.
The record
- CVE
- CVE-2025-53537
- Published
- Jul 23, 2025
- Updated
- Jul 23, 2025
- Vendor
- Open Information Security Foundation
- Product
- LibHTP
- Classifications
- CWE-401, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 23, 2025CVE publishedPublication date reported by the CVE source.
- Jul 23, 2025Record 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=< 0.5.51
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.
Weakness, pattern, technique
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