{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-4275 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-4275 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-4275 is a high-severity vulnerability in InsydeH2O, published on 11 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-4275 and fix it if it is affected.\n\nWhat it is: CVE-2025-4275 is a high-severity vulnerability in InsydeH2O, published on 11 Jun 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-4275 in the wild and no public exploit code.\n\nAffected product: InsydeH2O. 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-4275/ (Markdown: https://insights.sbomify.com/CVE-2025-4275/index.md)","id":"CVE-2025-4275","markdown":"https://insights.sbomify.com/CVE-2025-4275/index.md","name":"CVE-2025-4275","record":{"aliases":["GHSA-v9r5-7mg9-fwrr"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["security_bypass","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"UEFI firmware","requires_auth":"low_privilege","summary":"Attackers can bypass Secure Boot and execute arbitrary signed UEFI code by exploiting improper validation of UEFI variable attributes in InsydeH2O firmware.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Insyde","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"A vulnerability in the digital signature verification process does not properly validate variable attributes which allows an attacker to bypass signature verification by creating a non-authenticated NVRAM variable. An attacker may to execute arbitrary signed UEFI code and bypass Secure Boot.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-06-10","github_poc":3,"max_poc_stars":42,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-06-10T11:24:13Z","kind":"github_poc","ref":"https://github.com/NikolajSchlej/Hydroph0bia","stars":42,"title":"Binaries, drivers, PoCs and other stuff on Hydroph0bia vulnerability (CVE-2025-4275)"},{"date":"2026-01-12T11:38:28Z","kind":"github_poc","ref":"https://github.com/TheMalwareGuardian/CVE-2025-4275","stars":0,"title":"Analysis and exploitation of CVE-2025-4275 (Hydr0ph0bia), a Secure Boot trust-chain weakness where firmware variables are used to introduce attacker-controlled certificates trusted by subsequent boot components."},{"date":"2026-10-22T17:41:30Z","kind":"github_poc","ref":"https://github.com/Dorlander/hydrophobia-scanner","stars":0,"title":"Read-only defender scanner for CVE-2025-4275 (Hydroph0bia) on Insyde H2O firmware. Companion to Insyde SA-2025002 / CERT/CC VU#211341."}],"tier":"poc_unverified"},"has_fix":null,"headline":"SecureFlashDxe: Incorrect UEFI variable attributes check allows usage of invalid certificate","id":"CVE-2025-4275","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"UsbCoreDxe: improper input validation may lead to arbitrary code execution","id":"CVE-2025-4276"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2025-4273"},"products":["InsydeH2O"],"published":"2025-06-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-08-14","vendors":["Insyde Software"]},"summary":"Attackers can bypass Secure Boot and execute arbitrary signed UEFI code by exploiting improper validation of UEFI variable attributes in InsydeH2O firmware.","url":"https://insights.sbomify.com/CVE-2025-4275/"}