{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6177 exists.","fix":"No fix has been published for CVE-2025-6177 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6177 is a high-severity vulnerability in Google Chrome Os, published on 16 Jun 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-6177 and fix it if it is affected.\n\nWhat it is: CVE-2025-6177 is a high-severity vulnerability in Google Chrome Os, published on 16 Jun 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-6177 exists.\n\nAffected product: Google Chrome Os. 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-6177/ (Markdown: https://insights.sbomify.com/CVE-2025-6177/index.md)","id":"CVE-2025-6177","markdown":"https://insights.sbomify.com/CVE-2025-6177/index.md","name":"CVE-2025-6177","record":{"aliases":["GHSA-v9hm-xvm9-qqfr"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ChromeOS operating system","requires_auth":"none","summary":"Local attackers can gain root code execution on ChromeOS devices via a debug shell bypass, even when developer mode is blocked by policy.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ChromeOS","cpe":[{"product":"chrome_os","vendor":"google"}],"cvss":{"score":7.4,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Privilege Escalation in MiniOS in Google ChromeOS (16063.45.2 and potentially others) on enrolled devices allows a local attacker to gain root code execution via exploiting a debug shell (VT3 console) accessible through specific key combinations during developer mode entry and MiniOS access, even when developer mode is blocked by device policy or Firmware Write Protect (FWMP).","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":"ChromeOS MiniOS Root Code Execution Bypass While Dev Mode Blocked","id":"CVE-2025-6177","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:chrome_os","products":["google:chrome_os"],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"ChromeOS Extension Disablement and Developer Mode Bypass via ExtHang3r and ExtPrint3r Exploits","id":"CVE-2025-6179"},"packages":[],"prev":{"headline":"Brotli decompression bomb DoS in scrapy/scrapy","id":"CVE-2025-6176"},"products":["ChromeOS"],"published":"2025-06-16","related":[{"cvss_score":10,"headline":"Code injection in n/a","id":"CVE-2014-1708","kev_date_added":null,"published":"2014-03-16"},{"cvss_score":10,"headline":"Use after free in n/a","id":"CVE-2013-2833","kev_date_added":null,"published":"2013-04-16"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2013-0915","kev_date_added":null,"published":"2013-03-18"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2012-2864","kev_date_added":null,"published":"2012-08-22"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2012-4050","kev_date_added":null,"published":"2012-07-24"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-2171","kev_date_added":null,"published":"2011-05-24"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2011-1306","kev_date_added":null,"published":"2011-03-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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["Google"]},"summary":"Local attackers can gain root code execution on ChromeOS devices via a debug shell bypass, even when developer mode is blocked by policy.","url":"https://insights.sbomify.com/CVE-2025-6177/"}