{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69621 exists.","fix":"No fix has been published for CVE-2025-69621 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-69621 is a high-severity path traversal vulnerability in n/a, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-69621 and fix it if it is affected.\n\nWhat it is: CVE-2025-69621 is a high-severity path traversal vulnerability in n/a, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69621 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-69621/ (Markdown: https://insights.sbomify.com/CVE-2025-69621/index.md)","id":"CVE-2025-69621","markdown":"https://insights.sbomify.com/CVE-2025-69621/index.md","name":"CVE-2025-69621","record":{"aliases":["GHSA-p229-4rm7-jjq6"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Comic Book Reader","requires_auth":"none","summary":"Attackers can overwrite critical files via the import process, potentially leading to arbitrary code execution or information disclosure.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"An arbitrary file overwrite vulnerability in the file import process of Comic Book Reader v1.0.95 allows attackers to overwrite critical internal files, potentially leading to arbitrary code execution or exposure of sensitive information.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Path traversal in n/a","id":"CVE-2025-69621","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Null dereference in n/a","id":"CVE-2025-69624"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2025-69620"},"products":["n/a"],"published":"2026-02-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Attackers can overwrite critical files via the import process, potentially leading to arbitrary code execution or information disclosure.","url":"https://insights.sbomify.com/CVE-2025-69621/"}