# CVE-2025-23243: Missing authorization in Riva

> An attacker can exploit improper access control in NVIDIA Riva to tamper with data or cause a denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2025
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-wh9x-w9vv-rjf9

## What is CVE-2025-23243?

CVE-2025-23243 is a medium-severity missing authorization vulnerability in NVIDIA Riva, published on 11 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NVIDIA Riva contains a vulnerability where a user could cause an improper access control issue. A successful exploit of this vulnerability might lead to data tampering or denial of service.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Nvidia Riva.

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

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

## Is CVE-2025-23243 being exploited?

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

## Other vulnerabilities in NVIDIA Riva

- [CVE-2025-23242](https://insights.sbomify.com/CVE-2025-23242/): Missing authorization in Riva (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23243 is a medium-severity missing authorization vulnerability in NVIDIA Riva, published on 11 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-23243 in the wild and no public exploit code.

Affected product: NVIDIA Riva. 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-23243/ (Markdown: https://insights.sbomify.com/CVE-2025-23243/index.md)
```

## Sources

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

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