{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61146 exists.","fix":"No fix has been published for CVE-2025-61146 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-61146 is a medium-severity denial of service vulnerability in n/a, published on 23 Feb 2026. 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-61146 and fix it if it is affected.\n\nWhat it is: CVE-2025-61146 is a medium-severity denial of service vulnerability in n/a, published on 23 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61146 exists.\n\nAffected product: n/a. 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-61146/ (Markdown: https://insights.sbomify.com/CVE-2025-61146/index.md)","id":"CVE-2025-61146","markdown":"https://insights.sbomify.com/CVE-2025-61146/index.md","name":"CVE-2025-61146","record":{"aliases":["DEBIAN-CVE-2025-61146","GHSA-75j9-8g79-fp7r","UBUNTU-CVE-2025-61146"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"libsixel image library","requires_auth":"none","summary":"A memory leak in libsixel allows attackers to cause denial of service by exhausting system memory.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libsixel","vendor":"saitoha"}],"cvss":{"score":4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"saitoha libsixel until v1.8.7 was discovered to contain a memory leak via the component malloc_stub.c.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Denial of service in n/a","id":"CVE-2025-61146","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2025-61147"},"packages":[],"prev":{"headline":"Use after free in n/a","id":"CVE-2025-61145"},"products":["n/a"],"published":"2026-02-23","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-19635","kev_date_added":null,"published":"2019-12-08"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2019-19636","kev_date_added":null,"published":"2019-12-08"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2019-19637","kev_date_added":null,"published":"2019-12-08"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2019-19638","kev_date_added":null,"published":"2019-12-08"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2022-27044","kev_date_added":null,"published":"2022-04-08"},{"cvss_score":8.8,"headline":"Use after free in n/a","id":"CVE-2022-27046","kev_date_added":null,"published":"2022-04-08"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2020-21547","kev_date_added":null,"published":"2021-09-17"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-23","vendors":["n/a"]},"summary":"A memory leak in libsixel allows attackers to cause denial of service by exhausting system memory.","url":"https://insights.sbomify.com/CVE-2025-61146/"}