LiveActive security incident?Get immediate response
CVE Record

CVE-2021-25735: Validating Admission Webhook does not observe some previous fields

A security issue was discovered in kube-apiserver that could allow node updates to bypass a Validating Admission Webhook. Clusters are only affected by this vulnerability if they run a Validating Admission Webhook for Nodes that denies admission based at least partially on the old state of the Node object. Validating Admission Webhook does not observe some previous fields.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Kubernetes API server flaw can let highly privileged node updates bypass a specific kind of validating admission webhook. It matters when an organization relies on webhooks to block Node changes by comparing the new request to the previous Node state.

Executive priority

Prioritize review in Kubernetes environments where Node admission controls enforce security policy. The issue is not broadly exposed by default, but it can weaken controls that protect cluster integrity and availability.

Technical view

kube-apiserver may fail to present some previous Node fields to Validating Admission Webhooks. Affected clusters are those using Node webhooks that deny admission based partly on old Node object state. CVSS 6.5 reflects network reachability, low complexity, high required privileges, and high integrity and availability impact.

Likely exposure

Exposure appears limited to Kubernetes clusters with Validating Admission Webhooks covering Node updates and relying on prior Node state. Clusters without that design are not described as affected in the source bundle.

Exploitation context

The source bundle does not show KEV listing or active exploitation evidence. The CVSS vector requires high privileges, so this is most relevant to already privileged Kubernetes identities or compromised automation able to update Node objects.

Researcher notes

Evidence is specific but incomplete on exact fixed versions in the provided bundle. Focus analysis on admission webhook behavior for Node updates, old-object state dependencies, and vendor advisories rather than assuming all Kubernetes clusters are affected.

Mitigation direction

  • Review Kubernetes security advisory and distribution guidance for fixed versions.
  • Inventory ValidatingWebhookConfiguration rules that apply to Node resources.
  • Identify Node admission logic that depends on previous object state.
  • Upgrade kube-apiserver following vendor guidance if your version is affected.
  • Do not rely solely on affected webhook checks until remediated.

Validation and detection

  • Confirm Kubernetes and kube-apiserver versions against vendor advisories.
  • Review whether Node update webhooks compare old and new object state.
  • Check admission and audit logs for unexpected accepted Node updates.
  • Test remediated clusters with safe policy validation, not offensive payloads.
  • Document whether each cluster matches the affected configuration.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-372: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-25735 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H1.25.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2021-25735Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
KubernetesKubernetesunspecified, unspecified, unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-372 · source CWE mapping

Incomplete Internal State Distinction

Incomplete Internal State Distinction represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.