{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-69627 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-69627 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-69627 is a high-severity use after free vulnerability in n/a, published on 13 Apr 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-69627 and fix it if it is affected.\n\nWhat it is: CVE-2025-69627 is a high-severity use after free vulnerability in n/a, published on 13 Apr 2026. 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-69627 in the wild and no public exploit code.\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-69627/ (Markdown: https://insights.sbomify.com/CVE-2025-69627/index.md)","id":"CVE-2025-69627","markdown":"https://insights.sbomify.com/CVE-2025-69627/index.md","name":"CVE-2025-69627","record":{"aliases":["GHSA-phj3-hcm2-mjhc"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PDF editing software","requires_auth":"none","summary":"A heap use-after-free in Nitro PDF Pro's JavaScript mailDoc method allows attackers to cause application crashes via crafted input.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nitro_pdf_pro","vendor":"gonitro"}],"cvss":{"score":8.4,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"Nitro PDF Pro for Windows 14.41.1.4 contains a heap use-after-free vulnerability in the implementation of the JavaScript method this.mailDoc(). During execution, an internal XID object is allocated and then freed prematurely, after which the freed pointer is still passed into UI and logging helper functions. Because the freed memory region may contain unpredictable heap data or remnants of attacker-controlled JavaScript strings, downstream routines such as wcscmp() may process invalid or stale pointers. This can result in access violations and non-deterministic crashes.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Use after free in n/a","id":"CVE-2025-69627","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-69633"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2025-69624"},"products":["n/a"],"published":"2026-04-13","related":[{"cvss_score":8.8,"headline":"Memory corruption in Nitro Pro","id":"CVE-2016-8709","kev_date_added":null,"published":"2017-02-10"},{"cvss_score":8.8,"headline":"Memory corruption in Nitro Pro","id":"CVE-2016-8711","kev_date_added":null,"published":"2017-02-10"},{"cvss_score":8.8,"headline":"Memory corruption in Nitro Pro","id":"CVE-2016-8713","kev_date_added":null,"published":"2017-02-10"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2025-66769","kev_date_added":null,"published":"2026-04-13"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2025-69624","kev_date_added":null,"published":"2026-04-13"},{"cvss_score":5.5,"headline":"Information disclosure in n/a","id":"CVE-2025-67825","kev_date_added":null,"published":"2026-01-08"}],"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":"total"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"A heap use-after-free in Nitro PDF Pro's JavaScript mailDoc method allows attackers to cause application crashes via crafted input.","url":"https://insights.sbomify.com/CVE-2025-69627/"}