Skip to content
Fencer Intel
low 2.7

CVE-2025-4563 json

Nodes can bypass dynamic resource allocation authorization checks

published last yr. modified last mo. also EUVD-2025-18894 , GHSA-hj2p-8wj8-pfq4 , GO-2025-3774

cvss
2.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits
0
none known

Summary

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.

Patch / fix

  • go k8s.io/kubernetes 1.32.6, 1.33.2
  • kubernetes kubernetes 1.32.6, 1.33.2
  • kubernetes Debian 14, Debian 13, Debian 12 1.20.5+really1.20.2-1

debian advisories DEBIAN-CVE-2025-4563

  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250730T213748-1.1

opensuse advisories openSUSE-SU-2025:15405-1

  • kubernetes Azure Linux 3.0 1.30.10-9

azure linux advisories AZL-64304

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2025-4563 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-4563 updated cvss 2.7

kube-apiserver: NodeRestriction Admission Controller Dynamic Resource Allocation Bypass

  • Red Hat OpenShift Container Platform 4 openshift, openshift-clients, openshift-kubelet, openshift-hyperkube, openshift-kube-apiserver, openshift-kube-scheduler, +2 more
    affected: workaround, no fix available “Fix deferred”
  • Red Hat OpenShift Container Platform 4 openshift4/ose-hyperkube, openshift4/ose-kube-proxy, openshift4/ose-hyperkube-rhel9, openshift4/ose-kube-proxy-rhel9, ose-installer-kube-apiserver-artifacts-container
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.83% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L
GitHub 3.1 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
go k8s.io/kubernetes
>=1.32.0, <1.32.6
>=1.33.0, <1.33.2
1.32.6
1.33.2

Affected products

  • Kubernetes Kubernetes

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-863 Incorrect Authorization
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.