{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-9165 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-9165 is a low-severity denial of service vulnerability in Libtiff Libtiff, published on 19 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-9165 and fix it if it is affected.\n\nWhat it is: CVE-2025-9165 is a low-severity denial of service vulnerability in Libtiff Libtiff, published on 19 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-9165 in the wild and no public exploit code.\n\nAffected product: Libtiff Libtiff. 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-9165/ (Markdown: https://insights.sbomify.com/CVE-2025-9165/index.md)","id":"CVE-2025-9165","markdown":"https://insights.sbomify.com/CVE-2025-9165/index.md","name":"CVE-2025-9165","record":{"aliases":["ALPINE-CVE-2025-9165","AZL-66542","AZL-66545","BELL-CVE-2025-9165","DEBIAN-CVE-2025-9165","ECHO-0122-30ba-e03c","GHSA-64vg-6m9q-6vr3","MINI-8g47-qprw-7v97","OESA-2025-2190","OESA-2025-2191","UBUNTU-CVE-2025-9165"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"LibTIFF image library","requires_auth":"low_privilege","summary":"A memory leak in the tiffcmp command-line tool could lead to resource exhaustion, though its security impact is disputed by maintainers.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"libtiff","vendor":"libtiff"}],"cvss":{"score":2,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-404","name":"Improper Resource Shutdown or Release"},{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"A flaw has been found in LibTIFF 4.7.0. This affects the function _TIFFmallocExt/_TIFFCheckRealloc/TIFFHashSetNew/InitCCITTFax3 of the file tools/tiffcmp.c of the component tiffcmp. Executing manipulation can lead to memory leak. The attack is restricted to local execution. This attack is characterized by high complexity. It is indicated that the exploitability is difficult. The exploit has been published and may be used. There is ongoing doubt regarding the real existence of this vulnerability. This patch is called ed141286a37f6e5ddafb5069347ff5d587e7a4e0. It is best practice to apply a patch to resolve this issue. A researcher disputes the security impact of this issue, because \"this is a memory leak on a command line tool that is about to exit anyway\". In the reply the project maintainer declares this issue as \"a simple 'bug' when leaving the command line tool and (...) not a security issue at all\".","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":"LibTIFF tiffcmp tiffcmp.c InitCCITTFax3 memory leak","id":"CVE-2025-9165","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"libtiff:libtiff","products":["libtiff:libtiff"],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":9,"next":{"headline":"Rockwell Automation ControlLogix® 5580 V35.013 Denial-Of-Service","id":"CVE-2025-9166"},"packages":[],"prev":{"headline":"Multiple DLL Search Order Hijacking Vulnerabilities in Docker Desktop Installer for Windows","id":"CVE-2025-9164"},"products":["LibTIFF"],"published":"2025-08-19","related":[{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2004-1308","kev_date_added":null,"published":"2004-12-22"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2004-0929","kev_date_added":null,"published":"2004-10-26"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-61144","kev_date_added":null,"published":"2026-02-23"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-9533","kev_date_added":null,"published":"2016-11-22"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-9534","kev_date_added":null,"published":"2016-11-22"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-9535","kev_date_added":null,"published":"2016-11-22"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-9536","kev_date_added":null,"published":"2016-11-22"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-01","vendors":["n/a"]},"summary":"A memory leak in the tiffcmp command-line tool could lead to resource exhaustion, though its security impact is disputed by maintainers.","url":"https://insights.sbomify.com/CVE-2025-9165/"}