{"answers":{"affected":"It affects 2 products.","exploited":"Yes. Attackers have exploited CVE-2025-10585 in the wild since at least 23 Sep 2025.","fix":"Upgrade to a fixed version. US federal agencies must fix it by 14 Oct 2025.","what":"CVE-2025-10585 is a high-severity memory corruption vulnerability in Google Chrome, published on 24 Sep 2025. 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-10585 and fix it if it is affected.\n\nWhat it is: CVE-2025-10585 is a high-severity memory corruption vulnerability in Google Chrome, published on 24 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: Yes. Attackers have exploited CVE-2025-10585 in the wild since at least 23 Sep 2025.\n\nAffected product: Google Chrome. 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-10585/ (Markdown: https://insights.sbomify.com/CVE-2025-10585/index.md)","id":"CVE-2025-10585","markdown":"https://insights.sbomify.com/CVE-2025-10585/index.md","name":"CVE-2025-10585","record":{"aliases":["AZL-76335","DEBIAN-CVE-2025-10585","GHSA-hmrc-68hp-82x6"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Google Chrome","requires_auth":"none","summary":"Remote attackers can exploit heap corruption via crafted HTML pages in Google Chrome, potentially leading to code execution.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Chrome","cpe":[{"product":"chrome","vendor":"google"},{"product":"cadra","vendor":"siemens"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"}],"description":"Type confusion in V8 in Google Chrome prior to 140.0.7339.185 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-09-19","github_poc":1,"max_poc_stars":13,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-09-19T19:53:28Z","kind":"github_poc","ref":"https://github.com/AdityaBhatt3010/CVE-2025-10585-The-Chrome-V8-Zero-Day","stars":13,"title":"Google patched CVE-2025-10585, a Chrome V8 zero-day under active exploitation — here’s what it is, why it matters, and how to stay safe."}],"tier":"exploited"},"has_fix":true,"headline":"Google Chromium V8 Type Confusion","id":"CVE-2025-10585","indexable":true,"kev":{"dateAdded":"2025-09-23","dueDate":"2025-10-14","knownRansomwareCampaignUse":"Unknown","product":"Chromium V8","requiredAction":"Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.","vendorProject":"Google","vulnerabilityName":"Google Chromium V8 Type Confusion Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"google:chrome","products":["google:chrome"],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Community Events \u003c= 1.5.1 - Unauthenticated SQL Injection","id":"CVE-2025-10586"},"packages":[],"prev":{"headline":"Portabilis i-Educar educar_calendario_anotacao_cad.php cross site scripting","id":"CVE-2025-10584"},"products":["Chrome"],"published":"2025-09-24","related":[{"cvss_score":9.6,"headline":"Google Chromium GPU Heap Buffer Overflow","id":"CVE-2022-4135","kev_date_added":"2022-11-28","published":"2022-11-25"},{"cvss_score":9.6,"headline":"Google Chrome Use-After-Free","id":"CVE-2020-16017","kev_date_added":"2021-11-03","published":"2021-01-08"},{"cvss_score":9.6,"headline":"Google Chrome for Android UI Heap Buffer Overflow","id":"CVE-2020-16010","kev_date_added":"2021-11-03","published":"2020-11-03"},{"cvss_score":8.8,"headline":"Google Chromium V8 Out of Bounds Write","id":"CVE-2026-87491","kev_date_added":"2026-09-09","published":"2026-09-09"},{"cvss_score":8.8,"headline":"Google Chromium V8 Type Confusion","id":"CVE-2026-85046","kev_date_added":"2026-09-04","published":"2026-09-03"},{"cvss_score":8.8,"headline":"Google Chromium V8 Out-of-Bounds Read and Write","id":"CVE-2026-11645","kev_date_added":"2026-06-09","published":"2026-06-08"},{"cvss_score":8.8,"headline":"Google Dawn Use-After-Free","id":"CVE-2026-5281","kev_date_added":"2026-04-01","published":"2026-04-01"}],"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":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["Google"]},"summary":"Remote attackers can exploit heap corruption via crafted HTML pages in Google Chrome, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2025-10585/"}