Skip to content
major vulnerability· requires attention

Affects widely-used Intel AMT/Standard Manageability firmware; could disrupt enterprise remote management across many devices.

Hardware

CVE-2025-32008

8.7
High
EPSS 0.29%Patch availableFeb 11, 2026

DoS via unauthenticated network access to Intel AMT/Standard Manageability firmware.

common questions

Is CVE-2025-32008 being exploited?

Not confirmed. CVE-2025-32008 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.

How severe is CVE-2025-32008?

CVE-2025-32008 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-32008?

Yes. A fix has been recorded for CVE-2025-32008. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-32008 affect?

CVE-2025-32008 affects Intel AMT, Intel Standard Manageability firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-32008?

Apply latest Intel AMT firmware update; restrict AMT exposure.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Intel AMTIntel Standard Manageability firmware
impact

Denial of service via out-of-bounds write; unauthenticated network attacker can crash or render devices unavailable.

action required

Immediate action required

affected versions
Intel(R) AMT and Intel(R) Standard Manageability
  • affectedSee references

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free