# CVE-2025-30185: Privilege escalation in Intel UEFI reference platforms

> Active debug code in Intel UEFI firmware allows local attackers to escalate privileges and cause denial of service.

- **Severity:** High 8.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2025
- **Updated:** 14 Nov 2025
- **Also known as:** GHSA-xgfp-69mf-fpjr

## What is CVE-2025-30185?

CVE-2025-30185 is a high-severity vulnerability in Intel UEFI reference platforms, published on 11 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Active debug code for some Intel UEFI reference platforms within Ring 0: Kernel may allow a denial of service and escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable data alteration. This result may potentially occur via local 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 (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (high) and availability (high) impacts.

Weakness: CWE-489 (Active Debug Code)

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


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

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

## Is CVE-2025-30185 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30185 is a high-severity vulnerability in Intel UEFI reference platforms, published on 11 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30185 in the wild and no public exploit code.

Affected product: Intel UEFI reference platforms. 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-30185/ (Markdown: https://insights.sbomify.com/CVE-2025-30185/index.md)
```

## Sources

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

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