Is github.com/rancher/fleet 0.12 vulnerable?
Go · 22 releases from 0.12.0 to 0.12.21 · latest github.com/rancher/fleet is 0.16.3 · checked 18 Nov 2026
No known advisories in the last release
github.com/rancher/fleet 0.12.21, the last 0.12 release, has no known advisories. 14 advisories affect earlier 0.12.x releases, so update to 0.12.21.
go get github.com/rancher/fleet@v0.12.21Is your project on an affected github.com/rancher/fleet?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 0.12.x, affecting earlier releases
Fleet has PSS Bypass through addLabelsFromOptions in Fleet Agent in github.com/rancher/fleet
- Affected
- >=0.12.0 <0.12.15 · >=0.13.0 <0.13.11 · >=0.14.0 <0.14.6 · >=0.15.0 <0.15.2
- Fixed in
- 0.12.15, 0.13.11, 0.14.6, 0.15.2
Rancher Fleet has SSRF in Bundle Reader via Unvalidated Helm Repository URL in fleet.yaml in github.com/rancher/fleet
- Affected
- >=0.12.0 <0.12.15 · >=0.13.0 <0.13.11 · >=0.14.0 <0.14.6 · >=0.15.0 <0.15.2
- Fixed in
- 0.12.15, 0.13.11, 0.14.6, 0.15.2
Rancher Fleet has Unauthenticated Webhook: Regex Injection via Unsanitized Repository URL Components in github.com/rancher/fleet
- Affected
- >=0.12.0 <0.12.15 · >=0.13.0 <0.13.11 · >=0.14.0 <0.14.6 · >=0.15.0 <0.15.2
- Fixed in
- 0.12.15, 0.13.11, 0.14.6, 0.15.2
Rancher Fleet vulnerable to cross namespace secret disclosure via unvalidated `valuesFrom` references in Helm Deployer in github.com/rancher/fleet
- Affected
- >=0.12.0 <0.12.15 · >=0.13.0 <0.13.11 · >=0.14.0 <0.14.6 · >=0.15.0 <0.15.2
- Fixed in
- 0.12.15, 0.13.11, 0.14.6, 0.15.2
Rancher Fleet vulnerable to cross namespace secret disclosure via unvalidated `valuesFrom` references in Helm Deployer
- Affected
- >=0.15.0 <0.15.2 · >=0.14.0 <0.14.6 · >=0.13.0 <0.13.11 · >=0.12.0 <0.12.15
- Fixed in
- 0.12.15, 0.13.11, 0.14.6, 0.15.2
Rancher Fleet has SSRF in Bundle Reader via Unvalidated Helm Repository URL in fleet.yaml
- Affected
- >=0.15.0 <0.15.2 · >=0.14.0 <0.14.6 · >=0.13.0 <0.13.11 · >=0.12.0 <0.12.15
- Fixed in
- 0.12.15, 0.13.11, 0.14.6, 0.15.2
Rancher Fleet has Unauthenticated Webhook: Regex Injection via Unsanitized Repository URL Components
- Affected
- >=0.15.0 <0.15.2 · >=0.14.0 <0.14.6 · >=0.13.0 <0.13.11 · >=0.12.0 <0.12.15
- Fixed in
- 0.12.15, 0.13.11, 0.14.6, 0.15.2
Fleet has PSS Bypass through addLabelsFromOptions in Fleet Agent
- Affected
- >=0.15.0 <0.15.2 · >=0.14.0 <0.14.6 · >=0.13.0 <0.13.11 · >=0.12.0 <0.12.15
- Fixed in
- 0.12.15, 0.13.11, 0.14.6, 0.15.2
Fleet: Helm impersonation bypass of `RESTClientGetter` retains `cluster-admin` during template rendering in github.com/rancher/fleet
- Affected
- >=0.11.0 <0.11.13 · >=0.12.0 <0.12.14 · >=0.13.0 <0.13.10 · >=0.14.0 <0.14.5 · >=0.15.0 <0.15.1
- Fixed in
- 0.11.13, 0.12.14, 0.13.10, 0.14.5, 0.15.1
Fleet: Helm impersonation bypass of `RESTClientGetter` retains `cluster-admin` during template rendering
- Affected
- >=0.15.0 <0.15.1 · >=0.14.0 <0.14.5 · >=0.13.0 <0.13.10 · >=0.12.0 <0.12.14 · >=0.11.0 <0.11.13
- Fixed in
- 0.11.13, 0.12.14, 0.13.10, 0.14.5, 0.15.1
Rancher Fleet Helm Values are stored inside BundleDeployment in plain text in github.com/rancher/fleet
- Affected
- >=0.11.0 <0.11.10 · >=0.12.0 <0.12.6 · >=0.13.0 <0.13.1-0.20250806151509-088bcbea7edb
- Fixed in
- 0.11.10, 0.12.6, 0.13.1-0.20250806151509-088bcbea7edb
Rancher Fleet Helm Values are stored inside BundleDeployment in plain text
- Affected
- >=0.13.0 <0.13.1-0.20250806151509-088bcbea7edb · >=0.12.0 <0.12.6 · >=0.11.0 <0.11.10
- Fixed in
- 0.11.10, 0.12.6, 0.13.1-0.20250806151509-088bcbea7edb
Fleet doesn’t validate a server’s certificate when connecting through SSH in github.com/rancher/fleet
- 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
Fleet doesn’t validate a server’s certificate when connecting through SSH
- 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
Every github.com/rancher/fleet 0.12.x release
Affected: 0.12.0 to 0.12.14. 0.12.15 and later are not affected. Latest github.com/rancher/fleet: 0.16.3.
| Version | Known advisories |
|---|---|
| github.com/rancher/fleet 0.12.21 | None |
| github.com/rancher/fleet 0.12.20 | None |
| github.com/rancher/fleet 0.12.19 | None |
| github.com/rancher/fleet 0.12.18 | None |
| github.com/rancher/fleet 0.12.17 | None |
| github.com/rancher/fleet 0.12.16 | None |
| github.com/rancher/fleet 0.12.15 | None |
| github.com/rancher/fleet 0.12.14 | CVE-2026-44938, CVE-2026-44936, CVE-2026-44937, CVE-2026-44935, CVE-2026-44935, CVE-2026-44936, CVE-2026-44937, CVE-2026-44938 |
| github.com/rancher/fleet 0.12.13 | CVE-2026-44938, CVE-2026-44936, CVE-2026-44937, CVE-2026-44935, CVE-2026-44935, CVE-2026-44936, CVE-2026-44937, CVE-2026-44938, CVE-2026-41050, CVE-2026-41050 |
| github.com/rancher/fleet 0.12.12 | CVE-2026-44938, CVE-2026-44936, CVE-2026-44937, CVE-2026-44935, CVE-2026-44935, CVE-2026-44936, CVE-2026-44937, CVE-2026-44938, CVE-2026-41050, CVE-2026-41050 |
| github.com/rancher/fleet 0.12.11 | CVE-2026-44938, CVE-2026-44936, CVE-2026-44937, CVE-2026-44935, CVE-2026-44935, CVE-2026-44936, CVE-2026-44937, CVE-2026-44938, CVE-2026-41050, CVE-2026-41050 |
| github.com/rancher/fleet 0.12.10 | CVE-2026-44938, CVE-2026-44936, CVE-2026-44937, CVE-2026-44935, CVE-2026-44935, CVE-2026-44936, CVE-2026-44937, CVE-2026-44938, CVE-2026-41050, CVE-2026-41050 |
| github.com/rancher/fleet 0.12.9 | CVE-2026-44938, CVE-2026-44936, CVE-2026-44937, CVE-2026-44935, CVE-2026-44935, CVE-2026-44936, CVE-2026-44937, CVE-2026-44938, CVE-2026-41050, CVE-2026-41050 |
| github.com/rancher/fleet 0.12.8 | CVE-2026-44938, CVE-2026-44936, CVE-2026-44937, CVE-2026-44935, CVE-2026-44935, CVE-2026-44936, CVE-2026-44937, CVE-2026-44938, CVE-2026-41050, CVE-2026-41050 |
| github.com/rancher/fleet 0.12.7 | CVE-2026-44938, CVE-2026-44936, CVE-2026-44937, CVE-2026-44935, CVE-2026-44935, CVE-2026-44936, CVE-2026-44937, CVE-2026-44938, CVE-2026-41050, CVE-2026-41050 |
| github.com/rancher/fleet 0.12.6 | CVE-2026-44938, CVE-2026-44936, CVE-2026-44937, CVE-2026-44935, CVE-2026-44935, CVE-2026-44936, CVE-2026-44937, CVE-2026-44938, CVE-2026-41050, CVE-2026-41050 |
| github.com/rancher/fleet 0.12.5 | CVE-2026-44938, CVE-2026-44936, CVE-2026-44937, CVE-2026-44935, CVE-2026-44935, CVE-2026-44936, CVE-2026-44937, CVE-2026-44938, CVE-2026-41050, CVE-2026-41050, CVE-2024-52284, CVE-2024-52284 |
| github.com/rancher/fleet 0.12.4 | CVE-2026-44938, CVE-2026-44936, CVE-2026-44937, CVE-2026-44935, CVE-2026-44935, CVE-2026-44936, CVE-2026-44937, CVE-2026-44938, CVE-2026-41050, CVE-2026-41050, CVE-2024-52284, CVE-2024-52284 |
| github.com/rancher/fleet 0.12.3 | CVE-2026-44938, CVE-2026-44936, CVE-2026-44937, CVE-2026-44935, CVE-2026-44935, CVE-2026-44936, CVE-2026-44937, CVE-2026-44938, CVE-2026-41050, CVE-2026-41050, CVE-2024-52284, CVE-2024-52284 |
| github.com/rancher/fleet 0.12.2 | CVE-2026-44938, CVE-2026-44936, CVE-2026-44937, CVE-2026-44935, CVE-2026-44935, CVE-2026-44936, CVE-2026-44937, CVE-2026-44938, CVE-2026-41050, CVE-2026-41050, CVE-2024-52284, CVE-2024-52284 |
| github.com/rancher/fleet 0.12.1 | CVE-2026-44938, CVE-2026-44936, CVE-2026-44937, CVE-2026-44935, CVE-2026-44935, CVE-2026-44936, CVE-2026-44937, CVE-2026-44938, CVE-2026-41050, CVE-2026-41050, CVE-2024-52284, CVE-2024-52284, CVE-2025-23390, CVE-2025-23390 |
| github.com/rancher/fleet 0.12.0 | CVE-2026-44938, CVE-2026-44936, CVE-2026-44937, CVE-2026-44935, CVE-2026-44935, CVE-2026-44936, CVE-2026-44937, CVE-2026-44938, CVE-2026-41050, CVE-2026-41050, CVE-2024-52284, CVE-2024-52284, CVE-2025-23390, CVE-2025-23390 |
Which of your client projects are still on github.com/rancher/fleet 0.12?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/rancher/fleet version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/rancher/fleet versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.