{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1292 exists.","fix":"No fix has been published for CVE-2025-1292 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1292 is a medium-severity memory corruption vulnerability in Google Chrome, published on 15 Apr 2025. 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-1292 and fix it if it is affected.\n\nWhat it is: CVE-2025-1292 is a medium-severity memory corruption vulnerability in Google Chrome, published on 15 Apr 2025. 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-1292 exists.\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-1292/ (Markdown: https://insights.sbomify.com/CVE-2025-1292/index.md)","id":"CVE-2025-1292","markdown":"https://insights.sbomify.com/CVE-2025-1292/index.md","name":"CVE-2025-1292","record":{"aliases":["GHSA-44p4-ww39-jj4m"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ChromeOS TPM2 library","requires_auth":"high_privilege","summary":"An attacker with root access can exploit an out-of-bounds write in the TPM2 library to bypass OS verification and gain persistence on ChromeOS devices.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ChromeOS","cpe":[{"product":"chrome","vendor":"google"}],"cvss":{"score":6.7,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Out-Of-Bounds Write in TPM2 Reference Library in Google ChromeOS 122.0.6261.132  stable on Cr50 Boards allows an attacker with root access to gain persistence and \nbypass operating system verification via exploiting the NV_Read functionality during the Challenge-Response process.","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":"TPM2 Out-Of-Bounds Write Leading to Potential Operating System Verification Bypass in ChromeOS","id":"CVE-2025-1292","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:chrome","products":["google:chrome"],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"HashiCorp Hermes Improperly Validates AWS ALB JWTs, which May Lead to Authentication Bypass","id":"CVE-2025-1293"},"packages":[],"prev":{"headline":"Gutenberg Blocks by Kadence Blocks \u003c= 3.4.9 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'icon'","id":"CVE-2025-1291"},"products":["ChromeOS"],"published":"2025-04-15","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":"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":"2025-04-17","vendors":["Google"]},"summary":"An attacker with root access can exploit an out-of-bounds write in the TPM2 library to bypass OS verification and gain persistence on ChromeOS devices.","url":"https://insights.sbomify.com/CVE-2025-1292/"}