Skip to main content

Spring Cloud Azure CVE-2026-69854

| EUVDEUVD-2026-73791 HIGH
Improper Authentication (CWE-287)
2026-09-08 secure@microsoft.com GHSA-r33f-3f2c-x8cv
8.1
CVSS 3.1 · NVD
View

Attack ChainAIDerived

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

  1. Access
    Reach exposed Spring Cloud Azure app
  2. Delivery
    Send crafted authentication request
  3. Exploit
    Exploit improper authentication check
  4. Execution
    Bypass identity/authorization
  5. Impact
    Elevate privileges over network

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK

2 techniques across 2 tactics: Defense Evasion, Initial Access

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

Exploitation Conditions

Requires network access to a Java application that embeds Spring Cloud Azure at version 1.0.0 up to (but not including) 7.4.0. No authentication and no user interaction are needed (PR:N/UI:N), but the CVSS AC:H indicates exploitation depends on specific, non-trivial conditions - most plausibly a particular Spring Cloud Azure authentication/identity configuration or timing that the attacker must satisfy or win. Limiting factors: the flaw is confined to deployments actually using the vulnerable Spring Cloud Azure authentication path, the affected version window is bounded (fixed in 7.4.0), and the elevated CVSS complexity means it is not a guaranteed single-request compromise. The exact feature or configuration that must be present is not disclosed in the available advisory text and should be verified against the MSRC guidance.

Impact

This is a genuinely serious library vulnerability that warrants prompt patching, but the signals are mixed rather than screaming emergency. The CVSS 3.1 vector (8.1, AV:N/PR:N/UI:N) shows a network-reachable flaw needing no authentication and no user interaction, with full C:H/I:H/A:H impact consistent with an authentication/privilege-elevation bypass (CWE-287). The one factor holding it back from critical is AC:H - the vendor judges successful exploitation to require specific conditions or effort rather than a trivial single request. EPSS is low (0.64%, 49th percentile), which is consistent with AC:H and with the absence of any published exploit; it suggests exploitation is not (yet) trivially automatable or widespread. The CVE is NOT on CISA KEV and there is no public POC, so this is no public exploit identified at time of analysis - do not treat it as actively exploited. Net: a real, high-severity priority for anyone running Spring Cloud Azure below 7.4.0 because it is unauthenticated privilege escalation and a patch exists, but the AC:H and low EPSS argue this is a patch-in-the-normal-urgent-cycle item rather than a drop-everything zero-day. No conflicting signals were found between the vector and description; both point to a network, unauthenticated auth flaw.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends specially crafted requests to a Java application built on the vulnerable Spring Cloud Azure library, abusing the improper authentication logic to bypass identity checks and act as a higher-privileged principal. Because the CVSS complexity is High (AC:H), the attacker likely needs specific conditions met (e.g., particular authentication configuration or timing), but no credentials or victim interaction are required. No public exploit code exists at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.6% exploitation probability (EPSS)

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

Alert me

AnalysisAIv2 – Sep 29, 2026

Improper authentication handling in Spring Cloud Azure (versions 1.0.0 through releases before 7.4.0) allows an unauthenticated remote attacker to bypass authentication logic and elevate privileges within a Java application that embeds the library, yielding high confidentiality, integrity, and availability impact on the affected component and its Azure-connected resources. The 8.1 CVSS rating is moderated by a High attack-complexity metric, meaning the bypass hinges on a specific, non-trivial condition or configuration the attacker must satisfy rather than a single trivial request. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the EPSS score is low at 0.64 percent (49th percentile), so the risk is driven by exposure of vulnerable deployments rather than observed attack activity.

Earlier versions of this analysis (1)
v1 Sep 09, 2026 - 05:17 CVSS 9.0

Privilege elevation in Spring Cloud Azure (versions 1.0.0 up to but not including 7.4.0) lets a network-based, unauthenticated attacker bypass improper authentication logic (CWE-287) to gain elevated privileges. Reported by Microsoft (MSRC) with a vendor patch available; no public exploit identified at time of analysis and neither KEV nor EPSS/POC signals are present in the provided data.

RemediationAI

Vendor-released patch: upgrade Spring Cloud Azure to 7.4.0 or later, following the MSRC guidance at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69854. Because the library is typically pulled in transitively through a Spring Boot starter, verify the resolved dependency version (for example with mvn dependency:tree or Gradle dependency insight) rather than relying on the declared version, and pin/override the transitive artifact if needed. If immediate upgrade is not possible, compensating controls include placing the application behind an authenticated ingress or API gateway that enforces its own token validation so requests never reach the vulnerable authentication path unauthenticated - the trade-off is that this does not protect internal east-west calls that bypass the gateway; restricting network reachability of the affected service ports and endpoints to trusted callers via firewall, service mesh, or network policy - the trade-off is possible disruption of legitimate service-to-service or client traffic; and disabling or avoiding the specific Azure authentication/identity code path in the application until the upgrade lands - the trade-off is loss of the affected Azure credential or token features and potential application breakage. Monitor authentication failures and privilege-escalation indicators on exposed Java services in the meantime; no public exploit code is known, so detection should focus on anomalous identity/token flows rather than a specific signature.

Affected VersionsENISA

Spring Cloud Azure 1.0.0 <7.4.0

Affected Packages

euvd spring_cloud_azure fix: 7.4.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

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

Technical ContextAI · show details

The root cause class is CWE-287, Improper Authentication, in Spring Cloud Azure, Microsoft's Spring Boot integration library for Azure identity and service clients (for example Azure AD/Entra ID token acquisition and credential handling in Java applications). The CPE cpe:2.3:a:microsoft:spring_cloud:*:*:*:*:*:azure:*:* confirms the affected component is the Azure-targeted Spring Cloud module, not Spring Cloud itself. With AV:N/PR:N/UI:N the flaw is reachable over the network without credentials or user interaction, but AC:H indicates that successful exploitation requires the attacker to meet a particular precondition - most plausibly a specific authentication/identity configuration or a timing-sensitive condition in the library's auth path, as the advisory text does not disclose the exact feature or scenario. Impact is scoped S:U but rated C:H/I:H/A:H, meaning an attacker who wins the condition can act with elevated privilege inside the application's Azure-facing trust context. Fixed in Spring Cloud Azure 7.4.0. Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69854.

Know when Spring Cloud 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

NVD PRIMARY 8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
ENISA EUVD HIGH
vuln.today AI 8.1 HIGH

Network-reachable, unauthenticated improper authentication (AV:N/PR:N/UI:N) with high exploitation preconditions per vendor (AC:H); a full auth/privilege bypass yields C:H/I:H/A:H within the app's scope (S:U).

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

Primary rating from NVD.

CVSS VectorNVD

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

Lifecycle Timeline

5
Analysis Updated
Sep 29, 2026 - 20:12 vuln.today
v2 - CVSS changed
Severity Changed
Sep 29, 2026 - 20:07 NVD
CRITICAL HIGH
CVSS changed
Sep 29, 2026 - 20:07 NVD
9.0 (CRITICAL) 8.1 (HIGH)
Patch available
Sep 08, 2026 - 18:35 EUVD
CVE Published
Sep 08, 2026 - 18:19 nvd
CRITICAL 9.0

DescriptionNVD

Improper authentication in Spring Cloud Azure allows an unauthorized attacker to elevate privileges over a network.

Executive ViewAI

Why It Matters

Spring Cloud Azure, the library Java applications use to authenticate to Azure services, contains an authentication-bypass flaw (CVE-2026-69854, CVSS 8.1) that could allow a remote attacker to act with the affected application's Azure privileges, with high impact to confidentiality, integrity, and availability. Because the library is typically embedded in business-critical Java services holding live Azure credentials, exposure is not limited to the application itself but extends to every Azure-connected resource that service is authorized to reach. A vendor patch is available and no exploitation has been observed, so this should be managed as a scheduled remediation rather than an active incident.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.6%
Top 51% exploitable
Prevalence
Medium
Popular Azure integration library for Java Spring apps, but Azure-specific
Threat Intel
2
1 sources
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation More Likely
Data Quality
5 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 HIGH
CISA KEV No
Public POC No
EPSS 0.6%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
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
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: +5

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