{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-53537 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-53537 is a high-severity denial of service vulnerability in OISF libhtp, published on 23 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-53537 and fix it if it is affected.\n\nWhat it is: CVE-2025-53537 is a high-severity denial of service vulnerability in OISF libhtp, published on 23 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-53537 in the wild and no public exploit code.\n\nAffected product: OISF libhtp. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-53537/ (Markdown: https://insights.sbomify.com/CVE-2025-53537/index.md)","id":"CVE-2025-53537","markdown":"https://insights.sbomify.com/CVE-2025-53537/index.md","name":"CVE-2025-53537","record":{"aliases":["DEBIAN-CVE-2025-53537","GHSA-v3qq-h8mh-vph7","UBUNTU-CVE-2025-53537"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"HTTP parsing library","requires_auth":"none","summary":"A memory leak in LibHTP's LZMA handling allows attackers to exhaust system memory, causing denial of service and loss of visibility.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"libhtp","vendor":"oisf"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"LibHTP's memory leak with lzma can lead to resource starvation","id":"CVE-2025-53537","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Suricata's mishandling of data on HTTP2 stream 0 can lead to resource starvation","id":"CVE-2025-53538"},"packages":[],"prev":{"headline":"Roo Code allows Potential Remote Code Execution via .vscode/settings.json","id":"CVE-2025-53536"},"products":["libhtp"],"published":"2025-07-23","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-10243","kev_date_added":null,"published":"2019-04-04"},{"cvss_score":7.5,"headline":"LibHTP's unbounded header handling leads to denial service","id":"CVE-2024-45797","kev_date_added":null,"published":"2024-10-16"},{"cvss_score":7.5,"headline":"Excessive CPU used on malformed traffic","id":"CVE-2024-28871","kev_date_added":null,"published":"2024-04-04"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2015-0928","kev_date_added":null,"published":"2017-08-28"},{"cvss_score":5.3,"headline":"Security feature bypass in n/a","id":"CVE-2019-17420","kev_date_added":null,"published":"2019-10-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-23","vendors":["OISF"]},"summary":"A memory leak in LibHTP's LZMA handling allows attackers to exhaust system memory, causing denial of service and loss of visibility.","url":"https://insights.sbomify.com/CVE-2025-53537/"}