Skip to content
Fencer Intel
high 7.5

CVE-2025-53537 json

LibHTP's memory leak with lzma can lead to resource starvation

published last yr. modified 4mo ago also EUVD-2025-22472

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 43%
public exploits
0
none known

Summary

LibHTP is a security-aware parser for the HTTP protocol and its related bits and pieces. In versions 0.5.50 and below, there is a traffic-induced memory leak that can starve the process of memory, leading to loss of visibility. To workaround this issue, set `suricata.yaml app-layer.protocols.http.libhtp.default-config.lzma-enabled` to false. This issue is fixed in version 0.5.51.

Patch / fix

  • oisf libhtp 0.5.51
  • libhtp Debian 13 1:0.5.50-1+deb13u1

debian advisories DEBIAN-CVE-2025-53537

  • libhtp Ubuntu Pro 16.04 LTS 0.5.15-1ubuntu0.1~esm1
  • libhtp Ubuntu Pro 18.04 LTS 1:0.5.26-1ubuntu0.1~esm1
  • libhtp Ubuntu Pro 20.04 LTS 1:0.5.32-1ubuntu0.1~esm1
  • libhtp Ubuntu Pro 22.04 LTS 1:0.5.39-1ubuntu0.1~esm1
  • libhtp Ubuntu Pro 24.04 LTS 1:0.5.46-1ubuntu2+esm1

ubuntu advisories UBUNTU-CVE-2025-53537

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2025-53537 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • OISF libhtp

Classification

Weakness
  • CWE-401 Missing Release of Memory after Effective Lifetime

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.