# Fleet doesn’t validate a server’s certificate when connecting through SSH in github.com/rancher/fleet

Advisory record · `GHSA-xgpc-q899-67p8`

- **Identifiers:** `GHSA-xgpc-q899-67p8` · `CVE-2025-23390` · `GO-2025-3649`
- **State:** Confirmed
- **Severity:** CVSS 6.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-295](https://cwe.mitre.org/data/definitions/295.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 5 May 2025
- **Updated:** 3 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 May 2025, 16:13 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/rancher/fleet` (Go): affected `>=0.9.0-rc.1, <0.10.12 || >=0.11.0, <0.11.7 || >=0.12.0, <0.12.2`; fixed in `0.10.12`, `0.11.7`, `0.12.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Fleet (github.com/rancher/fleet) versions from 0.9.0-rc.1 up to but not including 0.10.12, from 0.11.0 up to but not including 0.11.7, and from 0.12.0 up to but not including 0.12.2 do not validate a server's certificate when connecting over SSH. The source gives few details on the attack scenario beyond that. Upgrade to 0.10.12, 0.11.7, 0.12.2, or a later release.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`, from CNA (suse)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0019, the 8th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 5 May 2025. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-xgpc-q899-67p8](https://github.com/advisories/GHSA-xgpc-q899-67p8)
- [OSV: GHSA-xgpc-q899-67p8](https://osv.dev/vulnerability/GHSA-xgpc-q899-67p8)
- <https://github.com/rancher/fleet/security/advisories/GHSA-xgpc-q899-67p8>
- <https://github.com/rancher/fleet/pull/3571>
- <https://github.com/rancher/fleet/pull/3572>
- <https://github.com/rancher/fleet/pull/3573>
- <https://github.com/rancher/fleet/releases/tag/v0.10.12>
- <https://github.com/rancher/fleet/releases/tag/v0.11.7>
- <https://github.com/rancher/fleet/releases/tag/v0.12.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xgpc-q899-67p8>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xgpc-q899-67p8/>. Everything for agents: <https://agentprime.io/llms.txt>.
