{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-62813 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-62813 is a vulnerability in coreboot-utils, published on 23 Oct 2025."},"fix_prompt":"Check this codebase for CVE-2025-62813 and fix it if it is affected.\n\nWhat it is: CVE-2025-62813 is a vulnerability in coreboot-utils, published on 23 Oct 2025. \nExploitation: There is no known exploitation of CVE-2025-62813 in the wild and no public exploit code.\n\nAffected product: coreboot-utils. 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-62813/ (Markdown: https://insights.sbomify.com/CVE-2025-62813/index.md)","id":"CVE-2025-62813","markdown":"https://insights.sbomify.com/CVE-2025-62813/index.md","name":"CVE-2025-62813","record":{"aliases":["ECHO-7c08-cb6b-2953","GHSA-r7j2-9m2h-fq95","openSUSE-SU-2025:15675-1","openSUSE-SU-2025:15678-1","openSUSE-SU-2025:15679-1","openSUSE-SU-2025:15688-1"],"analysis":null,"analysis_generated_by":null,"assigner":"mitre","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.","ecosystems":["openSUSE:Tumbleweed"],"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":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2025-62813","indexable":false,"kev":null,"kind":"cve_rejected","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2025"},"n_packages":4,"n_references":0,"next":{"headline":"Null dereference in n/a","id":"CVE-2025-62814"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["25.09-2.1"],"introduced":["0"],"last_affected":[],"package":"coreboot-utils","purl":"pkg:rpm/opensuse/coreboot-utils\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2025:15675-1"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["115.15.0-6.1"],"introduced":["0"],"last_affected":[],"package":"mozjs115","purl":"pkg:rpm/opensuse/mozjs115\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2025:15678-1"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["128.14.0-2.1"],"introduced":["0"],"last_affected":[],"package":"mozjs128","purl":"pkg:rpm/opensuse/mozjs128\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2025:15679-1"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["140.4.0-2.1"],"introduced":["0"],"last_affected":[],"package":"mozjs140","purl":"pkg:rpm/opensuse/mozjs140\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2025:15688-1"}],"prev":{"headline":"Not used","id":"CVE-2025-62812"},"products":[],"published":"2025-10-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"REJECTED","updated":"2025-10-29","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-62813/"}