# CVE-2025-4563: Nodes can bypass dynamic resource allocation authorization checks

> A compromised node can bypass authorization checks to create mirror pods accessing unauthorized dynamic resources, leading to privilege escalation.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** AZL-64304, CLEANSTART-2026-GL41768, CLEANSTART-2026-HE47180, DEBIAN-CVE-2025-4563, GHSA-hj2p-8wj8-pfq4, GO-2025-3774, MINI-28rj-f532-p652, MINI-4m6x-jrv6-97w9, MINI-4wj7-3fhh-p8f7, MINI-85wf-hhmw-84wx, MINI-8cqg-xhpw-wqr5, MINI-fw32-vr2x-xwvc, MINI-g9xg-679f-2rhw, MINI-p429-4pfr-6c3g, MINI-r2r5-76fc-v3pm, MINI-r3r7-j6c8-6xfx, MINI-rjx5-qwv7-3wq8, MINI-x9f2-f73r-p6xf

## What is CVE-2025-4563?

CVE-2025-4563 is a low-severity missing authorization vulnerability in Kubernetes, published on 23 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability exists in the NodeRestriction admission controller where nodes can bypass dynamic resource allocation authorization checks. When the DynamicResourceAllocation feature gate is enabled, the controller properly validates resource claim statuses during pod status updates but fails to perform equivalent validation during pod creation. This allows a compromised node to create mirror pods that access unauthorized dynamic resources, potentially leading to privilege escalation.

Weakness: CWE-20 (Improper Input Validation)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `k8s.io/kubernetes` | Go | From 1.32.0 | 1.32.6, 1.33.2 |
| `k8s.io/kubernetes` | Go | From 1.32.0 | 1.32.6 |
| `k8s.io/kubernetes` | Go | From 1.32.0 | 1.32.6 |
| `k8s.io/kubernetes` | Go | From 1.33.0 | 1.33.2 |
| `k8s.io/kubernetes` | Go | From 1.33.0 | 1.33.2 |

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

Upgrade k8s.io/kubernetes to a fixed version for your release line: 1.32.6 or 1.33.2.

## Is CVE-2025-4563 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4563 is a low-severity missing authorization vulnerability in Kubernetes, published on 23 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4563 in the wild and no public exploit code.

Affected packages and fixed versions:
- k8s.io/kubernetes (Go): affected from 1.32.0; fixed in 1.32.6, 1.33.2
- k8s.io/kubernetes (Go): affected from 1.32.0; fixed in 1.32.6
- k8s.io/kubernetes (Go): affected from 1.32.0; fixed in 1.32.6
- k8s.io/kubernetes (Go): affected from 1.33.0; fixed in 1.33.2
- k8s.io/kubernetes (Go): affected from 1.33.0; fixed in 1.33.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-4563/ (Markdown: https://insights.sbomify.com/CVE-2025-4563/index.md)
```

## Sources

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

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