cve.bz

CVE-2026-113823 Azure CycleCloud Information Disclosure Vulnerability

7.5 highEPSS 1.3%

High (7.5) in microsoft azure cyclecloud 8.9.2. EPSS 1.3% estimated probability of exploitation activity in the next 30 days.

On this page
Improper limitation of a pathname to a restricted directory ('path traversal') in Azure CycleCloud allows an unauthorized attacker to disclose information over a network.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
1.3% estimated probability of exploitation activity in the next 30 days; 71st percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-113823 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-113823?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-113823?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-113823 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-113823

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-113823](https://cve.bz/cve/badge/CVE-2026-113823.svg)](https://cve.bz/cve/CVE-2026-113823)

HTML:

<a href="https://cve.bz/cve/CVE-2026-113823"><img src="https://cve.bz/cve/badge/CVE-2026-113823.svg" alt="CVE-2026-113823"></a>

Affected

  • microsoft:azure cyclecloud 8.9.2

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Azure CycleCloud 8.9.2from 8.9.2 before 8.10.1

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON