dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2025-32008

HIGH · 8.6 CVSS v3.1 Published 2026-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An out-of-bounds write vulnerability exists in Intel(R) AMT and Intel(R) Standard Manageability firmware within Ring 3 User Applications. An unauthenticated network attacker with low complexity can exploit this to cause a denial of service on the affected system, resulting in high availability impact on the target and low availability impact on subsequent system operations.

MitigationApply the Intel firmware update for AMT and Standard Manageability to the patched version as specified in Intel's security advisory. For systems where firmware updates are not feasible, consider network-based mitigations such as restricting access to AMT management ports (typically 16992-16994) to authorized management networks only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Intel AMT or Standard Manageability is present
    Check system BIOS/UEFI settings under 'Intel AMT', 'Intel Management Engine', or 'Active Management Technology' settings, or use 'lspci' to look for 'Management Engine' or 'Active Management Technology' devices
    Affected if Intel AMT or Standard Manageability is present and enabled in firmware
  2. Determine if AMT user applications are running
    Check if the Intel AMT user space application is active by looking for the 'amt' service or process on typical AMT ports (16992, 16993 for HTTP; 16994, 16995 for HTTPS) using 'netstat -an | grep -E "1699[2-5]"' or equivalent network scanning tool
    Affected if AMT user applications are listening on network ports (even on localhost)
  3. Identify Intel ME/AMT firmware version
    Use Intel ME InfoTool, 'intelmetool' (if available), or check via the AMT web interface at http://localhost:16992 or https://localhost:16993 to retrieve the firmware version string
    Affected if The installed firmware version falls within the affected range for CVE-2025-32008 (compare against Intel advisory for specific version numbers)
  4. Verify network accessibility of AMT interfaces
    Perform a network scan from an external system or different network segment to confirm whether ports 16992-16995 are reachable, or review firewall rules and network configuration
    Affected if AMT management ports (16992-16995) are exposed to untrusted networks or the internet

A system is affected if Intel AMT or Standard Manageability is enabled with an unpatched firmware version within the affected range and the AMT user applications are network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Intel firmware update for AMT and Standard Manageability to the patched version as specified in Intel's security advisory. For systems where firmware updates are not feasible, consider network-based mitigations such as restricting access to AMT management ports (typically 16992-16994) to authorized management networks only.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32008 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32008 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data