{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-32008 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-32008 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-32008 is a high-severity memory corruption vulnerability in Intel(R) AMT and Intel(R) Standard Manageability, published on 10 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-32008 and fix it if it is affected.\n\nWhat it is: CVE-2025-32008 is a high-severity memory corruption vulnerability in Intel(R) AMT and Intel(R) Standard Manageability, published on 10 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-32008 in the wild and no public exploit code.\n\nAffected product: Intel(R) AMT and Intel(R) Standard Manageability. 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-32008/ (Markdown: https://insights.sbomify.com/CVE-2025-32008/index.md)","id":"CVE-2025-32008","markdown":"https://insights.sbomify.com/CVE-2025-32008/index.md","name":"CVE-2025-32008","record":{"aliases":["GHSA-9f53-h2mq-rm2m"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Intel AMT firmware","requires_auth":"none","summary":"A network-based attacker can cause a denial of service in Intel AMT firmware via an out-of-bounds write vulnerability.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"intel","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Out-of-bounds write in the firmware for the Intel(R) AMT and Intel(R) Standard Manageability within Ring 3: User Applications may allow a denial of service. Network adversary with an unauthenticated user combined with a low complexity attack may enable denial of service. This result may potentially occur via network access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (low) impacts.","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":"Memory corruption in Intel(R) AMT and Intel(R) Standard Manageability","id":"CVE-2025-32008","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused","id":"CVE-2025-32009"},"packages":[],"prev":{"headline":"Information disclosure in TDX","id":"CVE-2025-32007"},"products":["Intel(R) AMT and Intel(R) Standard Manageability"],"published":"2026-02-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-10","vendors":["n/a"]},"summary":"A network-based attacker can cause a denial of service in Intel AMT firmware via an out-of-bounds write vulnerability.","url":"https://insights.sbomify.com/CVE-2025-32008/"}