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

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.

Published: 2025-06-23 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-4563 is rated Low Risk (21.3/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.11%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-4563

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-19 0.02% 0.11% +0.09%
2 2025-11-21 0.10% 0.02% -0.08%
3 2025-11-18 — 0.10% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-4563

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
2.7 3.1 LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.2 1.4 [email protected]

Weakness enumeration for CVE-2025-4563

GitHub Security Advisory for CVE-2025-4563

GHSA-hj2p-8wj8-pfq4 · Severity: low · Ecosystem: go — kubernetes allows nodes to bypass dynamic resource allocation authorization checks

OS Trackers for CVE-2025-4563

vendor priority summary link
debian not yet assigned CVE-2025-4563 not yet assigned priority: Debian including 1 source packages (kubernetes), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-4563
redhat low — https://access.redhat.com/security/cve/CVE-2025-4563
suse medium CVE-2025-4563 severity moderate: SUSE including 81 source package names (govulncheck-vulndb-0.0.20250730T213748-1.1, govulncheck-vulndb-0.0.20250814T182633-160000.1.2, …), 279 product×package rows across 20 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (20 product lines)): Known Not Affected 277, Fixed 2. https://www.suse.com/security/cve/CVE-2025-4563/
ubuntu medium CVE-2025-4563 medium priority: Ubuntu including 1 source packages (kubernetes), 6 status rows across 6 suites (focal, jammy, noble, oracular, plucky, upstream): not-affected 3, DNE 1, ignored 1, needs-triage 1. https://ubuntu.com/security/CVE-2025-4563

Affected software / configurations for CVE-2025-4563

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-4563

cvelogic Threat Intelligence