CVE-2025-53793VulnerabilityPublished 12 Aug 2025Updated 13 Feb 2026

CVE-2025-53793: Microsoft Azure Stack Hub 2406 · Improper Authentication

Affects Microsoft Azure Stack Hub 2406Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.3% chance of exploitation in 30 days – higher than 71% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C

Base metrics

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

Temporal metrics

Exploit Code Maturity: Unproven
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Unproven: No exploit code is available, or an exploit is theoretical.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

cwe-22

What to do

Affected software

Product	Affected	Fixed in
Microsoft Azure Stack Hub 2406	Affected =1.0.0	Fixed in–

AI-suggested

1. Monitor Microsoft security advisories closely and apply official patches or updates for Azure Stack Hub 2406 as soon as they become available. 2. Until patches are released, implement strict network segmentation to restrict access to Azure Stack Hub management interfaces and services to trusted internal networks only. 3. Employ network intrusion detection and prevention systems (IDS/IPS) to detect anomalous access attempts targeting Azure Stack Hub components. 4. Enforce strong access control policies and multi-factor authentication (MFA) for all administrative and management interfaces related to Azure Stack Hub. 5. Conduct regular security audits and vulnerability assessments focusing on hybrid cloud infrastructure to identify and remediate potential exposure points. 6. Limit exposure of Azure Stack Hub endpoints to the internet or untrusted networks to reduce attack surface. 7. Maintain detailed logging and monitoring of access to Azure Stack Hub services to enable rapid detection and response to suspicious activities. 8. Educate IT and security teams about this specific vulnerability and the importance of timely patching and network controls in hybrid cloud environments.

Description

Improper authentication in Azure Stack allows an unauthorized attacker to disclose information over a network.

Impact

For European organizations, the impact of CVE-2025-53793 is significant due to the potential unauthorized disclosure of sensitive information hosted on Azure Stack Hub 2406. Confidentiality breaches could expose critical business data, customer information, or intellectual property, leading to regulatory compliance issues under GDPR and reputational damage. Since Azure Stack Hub is often deployed in hybrid cloud scenarios for sensitive workloads, attackers exploiting this vulnerability could gain insights into internal cloud configurations or operational data, facilitating further attacks or lateral movement. The absence of integrity or availability impact limits immediate operational disruption, but the confidentiality compromise alone is critical. Organizations in sectors such as finance, healthcare, and government, which heavily rely on Azure Stack for hybrid cloud deployments, are particularly at risk. The vulnerability's ease of exploitation without authentication increases the threat level, especially in environments with insufficient network segmentation or monitoring. European entities must consider the potential for targeted attacks leveraging this flaw to extract sensitive data remotely.

CWE-287Improper Authentication (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Libraries or Frameworks
Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Fake the Source of Data (opens in a new tab)
Utilizing REST's Trust in the System Resource to Obtain Sensitive Data (opens in a new tab)
Session Hijacking (opens in a new tab)
Token Impersonation (opens in a new tab)
Upload a Web Shell to a Web Server (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

msrc.microsoft.com/update-guide/vulnerability/CVE-2025-53793 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Feb 2026, 10:56 UTC

WeaknessesCWE-287

Technical details

References

Community reviews

Related threats