# CVE-2025-13281: Portworx Half-Blind SSRF in kube-controller-manager

> Authorized users can leak information from control plane host network endpoints via SSRF in kube-controller-manager when using in-tree Portworx StorageClass.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Dec 2025
- **Updated:** 15 Dec 2025
- **Also known as:** AZL-72382, AZL-72386, CLEANSTART-2026-FK82448, CLEANSTART-2026-KO57202, DEBIAN-CVE-2025-13281, ECHO-d43d-bac8-84e2, GHSA-r6j8-c6r2-37rr, GO-2025-4240, MINI-27hm-q2wf-7mr4, MINI-293q-ch4v-jpwg, MINI-2c3h-pr47-j69x, MINI-2pgx-ffvm-g22q, MINI-3wr8-ch72-2c25, MINI-525p-529r-rr42, MINI-62w8-cxqf-gxw9, MINI-734r-rpvv-wmrm, MINI-7hf9-9m7w-r63x, MINI-7rhv-j3ph-2qmr, MINI-848g-gjmh-pq5c, MINI-8g9x-xww5-g5j9, MINI-9p23-p575-hcjm, MINI-c7wq-3r7x-853x, MINI-cg9r-38q4-cv4q, MINI-cqg6-934h-x5vr, MINI-crx7-pg4h-jf7p, MINI-cwh4-wr4f-6ff4, MINI-fg87-xrwp-3p56, MINI-fr33-f4p5-7fw5, MINI-g2ff-wj7q-f2v2, MINI-gxq6-66v7-jq89, MINI-hvg3-r653-mp95, MINI-j39p-r324-q2rg, MINI-jr5p-8c3j-3858, MINI-p2v3-m8h5-x92h, MINI-p8m5-h44g-9j23, MINI-q297-9qg6-44v4, MINI-qrvq-pw3v-mpg7, MINI-v2wg-j5hm-9h2v, MINI-vrgm-r27q-pf5f, MINI-vv5f-cxgv-vfp2, MINI-w6pj-f94c-rxrh, MINI-xmcf-6v26-ggjv, OESA-2025-2815, OESA-2025-2816, OESA-2025-2817, OESA-2025-2818, OESA-2025-2819, OESA-2026-1162

## What is CVE-2025-13281?

CVE-2025-13281 is a medium-severity server-side request forgery vulnerability in Kubernetes, published on 14 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Weakness: CWE-918 (Server-Side Request Forgery)

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

7 open source packages ship an affected version, including k8s.io/kubernetes.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `k8s.io/kubernetes` | Go | All versions | 1.32.10, 1.33.6, 1.34.2 |
| `k8s.io/kubernetes` | Go | All versions | 1.32.10 |
| `k8s.io/kubernetes` | Go | All versions | 1.32.10 |
| `k8s.io/kubernetes` | Go | From 1.33.0-alpha.0 | 1.33.6 |
| `k8s.io/kubernetes` | Go | From 1.33.0-alpha.0 | 1.33.6 |
| `k8s.io/kubernetes` | Go | From 1.34.0-alpha.0 | 1.34.2 |
| `k8s.io/kubernetes` | Go | From 1.34.0-alpha.0 | 1.34.2 |

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

Upgrade k8s.io/kubernetes to a fixed version for your release line: 1.32.10, 1.33.6 or 1.34.2.

## Is CVE-2025-13281 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13281 is a medium-severity server-side request forgery vulnerability in Kubernetes, published on 14 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13281 in the wild and no public exploit code.

Affected packages and fixed versions:
- k8s.io/kubernetes (Go): affected all versions; fixed in 1.32.10, 1.33.6, 1.34.2
- k8s.io/kubernetes (Go): affected all versions; fixed in 1.32.10
- k8s.io/kubernetes (Go): affected all versions; fixed in 1.32.10
- k8s.io/kubernetes (Go): affected from 1.33.0-alpha.0; fixed in 1.33.6
- k8s.io/kubernetes (Go): affected from 1.33.0-alpha.0; fixed in 1.33.6
- k8s.io/kubernetes (Go): affected from 1.34.0-alpha.0; fixed in 1.34.2
- k8s.io/kubernetes (Go): affected from 1.34.0-alpha.0; fixed in 1.34.2

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-13281/ (Markdown: https://insights.sbomify.com/CVE-2025-13281/index.md)
```

## Sources

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

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