{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-6044 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-6044 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6044 is a medium-severity authentication bypass vulnerability in Google Chrome Os, published on 7 Jul 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-6044 and fix it if it is affected.\n\nWhat it is: CVE-2025-6044 is a medium-severity authentication bypass vulnerability in Google Chrome Os, published on 7 Jul 2025. 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-6044 in the wild and no public exploit code.\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-6044/ (Markdown: https://insights.sbomify.com/CVE-2025-6044/index.md)","id":"CVE-2025-6044","markdown":"https://insights.sbomify.com/CVE-2025-6044/index.md","name":"CVE-2025-6044","record":{"aliases":["GHSA-p4mw-xc4p-683j"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ChromeOS stylus tools","requires_auth":"none","summary":"Physical attackers can bypass the lock screen and access user files on ChromeOS devices by exploiting the stylus screen capture feature.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ChromeOS","cpe":[{"product":"chrome_os","vendor":"google"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"An Improper Access Control vulnerability in the Stylus Tools component of Google ChromeOS version 16238.64.0 on the garaged stylus devices allows a physical attacker to bypass the lock screen and access user files by removing the stylus while the device is closed and using the screen capture feature.","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":"Auth bypass in ChromeOS","id":"CVE-2025-6044","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:chrome_os","products":["google:chrome_os"],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2025-6046"},"packages":[],"prev":{"headline":"Missing authorization in Malcure Malware Shield — Removal, Repair, Monitor","id":"CVE-2025-6043"},"products":["ChromeOS"],"published":"2025-07-07","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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-07-09","vendors":["Google"]},"summary":"Physical attackers can bypass the lock screen and access user files on ChromeOS devices by exploiting the stylus screen capture feature.","url":"https://insights.sbomify.com/CVE-2025-6044/"}