# CVE-2025-13914: Apstra: SSH host key validation vulnerability for managed devices

> An unauthenticated MITM attacker can bypass SSH host key validation to impersonate managed devices and capture user credentials.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N/R:U/RE:M`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-3gg3-cwcp-3cpw

## What is CVE-2025-13914?

CVE-2025-13914 is a high-severity vulnerability in Juniper Networks Apstra, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Key Exchange without Entity Authentication vulnerability in the SSH implementation of Juniper Networks Apstra allows a unauthenticated, MITM 

attacker to impersonate managed devices.

Due to insufficient SSH host key validation an attacker can perform a machine-in-the-middle attack on the SSH connections from Apstra to managed devices, enabling an attacker to impersonate a managed device and capture user credentials.

This issue affects all versions of Apstra before 6.1.1.

Weakness: CWE-322 (Key Exchange without Entity Authentication)

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

It affects 1 product.


Products: Juniper Apstra.

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

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

## Is CVE-2025-13914 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13914 is a high-severity vulnerability in Juniper Networks Apstra, published on 9 Apr 2026. 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-13914 in the wild and no public exploit code.

Affected product: Juniper Networks Apstra. 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-13914/ (Markdown: https://insights.sbomify.com/CVE-2025-13914/index.md)
```

## Sources

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

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