Skip to main content

Azure Kubernetes Configuration CVE-2026-83938

| EUVDEUVD-2026-108541 CRITICAL
Missing Authentication for Critical Function (CWE-306)
2026-10-22 microsoft GHSA-2vxx-fgvw-2r33
10.0
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach service endpoint over network
  2. Exploit
    Invoke critical function lacking authentication
  3. Execution
    Elevate privileges across scope boundary
  4. Impact
    Compromise confidentiality, integrity and availability

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Per CVSS AV:N/AC:L/PR:N/UI:N there are no special preconditions in terms of authentication or user interaction: a network-positioned attacker can reach a critical function that is missing authentication (CWE-306) and elevate privileges. The exact critical function, protocol, and trigger are not described in the available sources. The principal limiting factor is that Azure Kubernetes Configuration Service is a Microsoft-managed cloud service: network reachability to the vulnerable endpoint and whether Microsoft has already remediated it server-side govern real-world exposure more than any customer-side configuration. No customer-side non-default configuration is stated as required.

Impact

Signals mostly align toward high priority. The CVSS 3.1 base is 10.0 with AV:N/AC:L/PR:N/UI:N and a scope change (S:C) plus full C:H/I:H/A:H impact, meaning an unauthenticated network attacker can elevate privileges with impact crossing a security boundary - consistent with CWE-306 (missing authentication for a critical function). The vuln.today decision label is act_now, which is the strongest urgency signal present. However, the temporal metrics temper the raw score: E:U (Exploit Code Maturity: Unproven) and the absence of any POC or exploit reference mean there is no public exploit identified at time of analysis, and the CVE is NOT in CISA KEV, so there is no confirmed active exploitation. No EPSS score was supplied, so exploitation probability cannot be quantified from the input. A key nuance: Azure Kubernetes Configuration Service is a Microsoft-operated cloud service, and the official fix (RL:O, patch available from vendor) is typically applied server-side by Microsoft rather than by customers - so real-world customer exposure may already be reduced regardless of the 10.0 score. Treat as act_now per the decision label, but note the exploitation status is unproven, not weaponized.

Exploit ScenarioDerived

An attacker with network reach to the Azure Kubernetes Configuration Service invokes a critical function that fails to enforce authentication, obtaining elevated privileges without credentials or user interaction. Because the CVSS scope is changed (S:C), the gained privileges can affect resources beyond the vulnerable component. No public exploit code or PoC reference was provided, and exploit maturity is rated Unproven.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.7% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 22, 2026

Privilege elevation in Azure Kubernetes Configuration Service is possible for unauthenticated network attackers because a critical function lacks authentication, and the CVSS 3.1 base score is 10.0. Because the service is Microsoft-managed, real-world exposure depends on network reachability to the vulnerable endpoint and on whether Microsoft has already completed server-side remediation; no customer-side non-default configuration is stated as required. Vendor patch information is available and the vuln.today priority label is act_now; no public exploit identified at time of analysis.

RemediationAI

Apply the vendor update described in the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83938; the provided data says a vendor patch is available but does not list an exact fixed version. Because Azure Kubernetes Configuration Service is Microsoft-managed, confirm with Microsoft whether server-side remediation is complete, as network reachability to the vulnerable endpoint is the main exposure factor in the assessment. No customer-side workaround or non-default configuration requirement is stated in the available data.

Affected VersionsENISA

Azure Kubernetes Configuration Service - (version not specified)

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-306 is Missing Authentication for Critical Function: the affected capability can be invoked without proving identity, and the CVSS vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) assesses a network-reachable, unauthenticated attacker with no user interaction and high confidentiality, integrity, and availability impact, with scope change. The supplied tags classify the issue as an authentication bypass involving Kubernetes and Microsoft. The CPE identifies microsoft:azure_kubernetes_configuration_service with a wildcard version, so the provided data does not enumerate affected builds; the exact critical function, protocol, and trigger are not described in the available sources. Azure Kubernetes Configuration Service is a Microsoft-managed cloud service, so the server-side deployment state governs exposure more than customer configuration, and the vendor reference is the MSRC update guide.

Know when Azure Kubernetes Configuration Service gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 10.0 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 10.0 CRITICAL

Missing authentication (CWE-306) on a network-reachable critical function gives AV:N/AC:L/PR:N/UI:N; privilege elevation crossing a boundary justifies S:C with full C:H/I:H/A:H.

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Missing authentication for critical function in Azure Kubernetes Configuration Service allows an unauthorized attacker to elevate privileges over a network.

Executive ViewAI

Why It Matters

A critical vulnerability in Microsoft's Azure Kubernetes Configuration Service (AKS Configuration Service) allows unauthenticated network attackers to elevate privileges. This affects the managed service underlying many AKS deployments, so any organization relying on AKS for container orchestration could be at risk. Leadership should prioritize immediate verification of Microsoft's server-side remediation and assess any exposure to the vulnerable endpoint.

Business Impact: Severe
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.7%
Top 49% exploitable
Prevalence
High
Core configuration/GitOps component for widely-deployed Azure Kubernetes Service
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:N/A
Social Media
1
Sightings
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.7%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Very High

Priority Score

51
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy