# CVE-2025-10262: An unsanitized format validation vulnerability in Nokia SR Linux

> An authenticated user can execute arbitrary commands with superuser privileges due to unsanitized format validation in Nokia SR Linux.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:H/A: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:** 16 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-h3gf-qq8m-r4r7

## What is CVE-2025-10262?

CVE-2025-10262 is a medium-severity command injection vulnerability in Nokia SR Linux, published on 16 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Nokia SR Linux is vulnerable to local privilege escalation vulnerability due to unsanitized format validation. Successful exploitation of this vulnerability may allow an authenticated user to execute arbitrary commands with superuser privileges.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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


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

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

## Is CVE-2025-10262 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10262 is a medium-severity command injection vulnerability in Nokia SR Linux, published on 16 Jun 2026. 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-10262 in the wild and no public exploit code.

Affected product: Nokia SR Linux. 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-10262/ (Markdown: https://insights.sbomify.com/CVE-2025-10262/index.md)
```

## Sources

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

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