{"answers":{"affected":"It affects 16 products.","exploited":"Yes. Attackers have exploited CVE-2025-47827 in the wild since at least 14 Oct 2025.","fix":"No fix has been published for CVE-2025-47827 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 4 Nov 2025.","what":"CVE-2025-47827 is a medium-severity vulnerability in Microsoft Windows 10 1507, published on 5 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-47827 and fix it if it is affected.\n\nWhat it is: CVE-2025-47827 is a medium-severity vulnerability in Microsoft Windows 10 1507, published on 5 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2025-47827 in the wild since at least 14 Oct 2025.\n\nAffected product: Microsoft Windows 10 1507. 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-47827/ (Markdown: https://insights.sbomify.com/CVE-2025-47827/index.md)","id":"CVE-2025-47827","markdown":"https://insights.sbomify.com/CVE-2025-47827/index.md","name":"CVE-2025-47827","record":{"aliases":["GHSA-pww7-j9v6-xc6j"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IGEL OS","requires_auth":"none","summary":"Attackers can bypass Secure Boot in IGEL OS by exploiting improper signature verification in the flash driver, allowing unverified root filesystems to be mounted.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"igel_os","vendor":"igel"},{"product":"windows_10_1507","vendor":"microsoft"},{"product":"windows_10_1607","vendor":"microsoft"},{"product":"windows_10_1809","vendor":"microsoft"},{"product":"windows_10_21h2","vendor":"microsoft"},{"product":"windows_10_22h2","vendor":"microsoft"},{"product":"windows_11_22h2","vendor":"microsoft"},{"product":"windows_11_23h2","vendor":"microsoft"},{"product":"windows_11_24h2","vendor":"microsoft"},{"product":"windows_11_25h2","vendor":"microsoft"},{"product":"windows_server_2012","vendor":"microsoft"},{"product":"windows_server_2016","vendor":"microsoft"},{"product":"windows_server_2019","vendor":"microsoft"},{"product":"windows_server_2022","vendor":"microsoft"},{"product":"windows_server_2022_23h2","vendor":"microsoft"},{"product":"windows_server_2025","vendor":"microsoft"}],"cvss":{"score":4.6,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"In IGEL OS before 11, Secure Boot can be bypassed because the igel-flash-driver module improperly verifies a cryptographic signature. Ultimately, a crafted root filesystem can be mounted from an unverified SquashFS image.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-05-20","github_poc":1,"max_poc_stars":4,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-05-20T10:42:11Z","kind":"github_poc","ref":"https://github.com/Zedeldi/CVE-2025-47827","stars":4,"title":"PoC and vulnerability report for CVE-2025-47827."}],"tier":"exploited"},"has_fix":null,"headline":"IGEL OS Use of a Key Past its Expiration Date","id":"CVE-2025-47827","indexable":true,"kev":{"dateAdded":"2025-10-14","dueDate":"2025-11-04","knownRansomwareCampaignUse":"Unknown","product":"IGEL OS","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":"IGEL","vulnerabilityName":"IGEL OS Use of a Key Past its Expiration Date Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"microsoft:windows_10_1507","products":["microsoft:windows_10_1507","microsoft:windows_10_1607","microsoft:windows_10_1809","microsoft:windows_10_21h2","microsoft:windows_10_22h2","microsoft:windows_11_22h2","microsoft:windows_11_23h2","microsoft:windows_11_24h2","microsoft:windows_11_25h2","microsoft:windows_server_2012","microsoft:windows_server_2016","microsoft:windows_server_2019","microsoft:windows_server_2022","microsoft:windows_server_2022_23h2","microsoft:windows_server_2025"],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"@lumieducation/h5p-server Fails to Sanitize Plain Text Strings","id":"CVE-2025-47828"},"packages":[],"prev":{"headline":"Hardcoded credentials in License Plate Reader","id":"CVE-2025-47824"},"products":["n/a"],"published":"2025-06-05","related":[],"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":"partial"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["n/a"]},"summary":"Attackers can bypass Secure Boot in IGEL OS by exploiting improper signature verification in the flash driver, allowing unverified root filesystems to be mounted.","url":"https://insights.sbomify.com/CVE-2025-47827/"}