# CVE-2025-22392: Information disclosure in Intel(R) AMT and Intel(R) Standard Manageability

> A privileged user can exploit an out-of-bounds read in Intel AMT firmware to disclose sensitive information via network access.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2025
- **Updated:** 12 Aug 2025
- **Also known as:** GHSA-8jgq-q52v-cx7m

## What is CVE-2025-22392?

CVE-2025-22392 is a medium-severity vulnerability in Intel(R) AMT and Intel(R) Standard Manageability, published on 12 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Out-of-bounds read in firmware for some Intel(R) AMT and Intel(R) Standard Manageability may allow a privileged user to potentially enable information disclosure via network access.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-22392?


## How do I fix CVE-2025-22392?

No fix has been published for CVE-2025-22392 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-22392 being exploited?

There is no known exploitation of CVE-2025-22392 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22392 and fix it if it is affected.

What it is: CVE-2025-22392 is a medium-severity vulnerability in Intel(R) AMT and Intel(R) Standard Manageability, published on 12 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-22392 in the wild and no public exploit code.

Affected 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.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-22392/ (Markdown: https://insights.sbomify.com/CVE-2025-22392/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22392
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22392
- OSV: https://osv.dev/vulnerability/CVE-2025-22392

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-22392/
Summaries are generated and may contain mistakes; the official description above is the record.