Loading vulnerability…
CVE-2025-59291 is an elevation of privilege vulnerability affecting Confidential Azure Container Instances. According to the provided content, the flaw is caused by external control of a file name or path, indicating that attacker-influenced path or filename handling within the container environment can be abused. The available information states that an authorized or privileged attacker can exploit this issue locally within the container environment to elevate privileges. No public technical details were provided in the supplied content regarding the specific vulnerable component, function, code path, affected versions, or exact exploitation sequence.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A privilege escalation issue in Microsoft Compute Gallery mentioned as part of Microsoft Azure's 2025 vulnerability history.
A vulnerability in Confidential Azure Container Instances allowing privileged attackers to elevate privileges locally via external control of file names or paths.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.