# CVE-2025-61985: Command injection in OpenSSH

> OpenSSH allows null characters in ssh URIs, enabling code execution via ProxyCommand when specific configurations are used.

- **Severity:** Low 3.6 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2025
- **Updated:** 15 Oct 2026
- **Also known as:** ALPINE-CVE-2025-61985, AZL-68228, AZL-68292, BELL-CVE-2025-61985, CLSA-2026-1767627264, CLSA-2026-1767627533, CLSA-2026-1767627828, DEBIAN-CVE-2025-61985, ECHO-c49b-d8dd-91e2, GHSA-8gmf-r74v-362p, JLSEC-2025-8, UBUNTU-CVE-2025-61985

## What is CVE-2025-61985?

CVE-2025-61985 is a low-severity command injection vulnerability in OpenBSD OpenSSH, published on 6 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ssh in OpenSSH before 10.1 allows the '\0' character in an ssh:// URI, potentially leading to code execution when a ProxyCommand is used.

Weakness: CWE-158 (Improper Neutralization of Null Byte or NUL Character)

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


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

Upgrade to a fixed version.

## Is CVE-2025-61985 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61985 is a low-severity command injection vulnerability in OpenBSD OpenSSH, published on 6 Oct 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-61985 in the wild and no public exploit code.

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

## Sources

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

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