# CVE-2025-20099: Privilege escalation in Intel(R) Rapid Storage Technology installation software

> An authenticated local user can escalate privileges due to improper access control in Intel Rapid Storage Technology installation software.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Aug 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-gw2r-pf7h-382c

## What is CVE-2025-20099?

CVE-2025-20099 is a medium-severity vulnerability in Intel(R) Rapid Storage Technology installation software, published on 12 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Improper access control for some Intel(R) Rapid Storage Technology installation software may allow an authenticated user to potentially enable escalation of privilege via local access.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-20099 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-20099 is a medium-severity vulnerability in Intel(R) Rapid Storage Technology installation software, published on 12 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-20099 in the wild and no public exploit code.

Affected product: Intel(R) Rapid Storage Technology installation software. 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-20099/ (Markdown: https://insights.sbomify.com/CVE-2025-20099/index.md)
```

## Sources

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

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