MSRC_CVE-2025-59291
Vulnerability from csaf_microsoft - Published: 2025-10-14 07:00 - Updated: 2025-10-14 07:00| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: 12304 | — |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: 1 | — |
{
"document": {
"acknowledgments": [
{
"names": [
"Microsoft Offensive Research \u0026amp; Security Engineering"
]
},
{
"names": [
"Microsoft Offensive Research \u0026amp; Security Engineering"
]
}
],
"aggregate_severity": {
"namespace": "https://www.microsoft.com/en-us/msrc/security-update-severity-rating-system",
"text": "Critical"
},
"category": "csaf_security_advisory",
"csaf_version": "2.0",
"distribution": {
"text": "Public",
"tlp": {
"label": "WHITE",
"url": "https://www.first.org/tlp/"
}
},
"lang": "en-US",
"notes": [
{
"category": "general",
"text": "To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle",
"title": "Additional Resources"
},
{
"category": "legal_disclaimer",
"text": "The information provided in the Microsoft Knowledge Base is provided \\\"as is\\\" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.",
"title": "Disclaimer"
},
{
"category": "general",
"text": "Required. The vulnerability documented by this CVE requires customer action to resolve.",
"title": "Customer Action"
}
],
"publisher": {
"category": "vendor",
"contact_details": "secure@microsoft.com",
"name": "Microsoft Security Response Center",
"namespace": "https://msrc.microsoft.com"
},
"references": [
{
"category": "self",
"summary": "CVE-2025-59291 Confidential Azure Container Instances Elevation of Privilege Vulnerability - HTML",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-59291"
},
{
"category": "self",
"summary": "CVE-2025-59291 Confidential Azure Container Instances Elevation of Privilege Vulnerability - CSAF",
"url": "https://msrc.microsoft.com/csaf/advisories/2025/msrc_cve-2025-59291.json"
},
{
"category": "external",
"summary": "Microsoft Exploitability Index",
"url": "https://www.microsoft.com/en-us/msrc/exploitability-index?rtc=1"
},
{
"category": "external",
"summary": "Microsoft Support Lifecycle",
"url": "https://support.microsoft.com/lifecycle"
},
{
"category": "external",
"summary": "Common Vulnerability Scoring System",
"url": "https://www.first.org/cvss"
}
],
"title": "Confidential Azure Container Instances Elevation of Privilege Vulnerability",
"tracking": {
"current_release_date": "2025-10-14T07:00:00.000Z",
"generator": {
"date": "2026-02-22T17:24:07.886Z",
"engine": {
"name": "MSRC Generator",
"version": "1.0"
}
},
"id": "msrc_CVE-2025-59291",
"initial_release_date": "2025-10-14T07:00:00.000Z",
"revision_history": [
{
"date": "2025-10-14T07:00:00.000Z",
"legacy_version": "1",
"number": "1",
"summary": "Information published."
}
],
"status": "final",
"version": "1"
}
},
"vulnerabilities": [
{
"cve": "CVE-2025-59291",
"cwe": {
"id": "CWE-73",
"name": "External Control of File Name or Path"
},
"notes": [
{
"category": "general",
"text": "Microsoft",
"title": "Assigning CNA"
},
{
"category": "faq",
"text": "An attacker could trick the system into mounting a malicious file share to a sensitive location, allowing them to run harmful code.",
"title": "How could an attacker exploit this vulnerability?"
},
{
"category": "faq",
"text": "The attacker could gain code execution within the confidential ACI sidecar container, escalating from host control to confidential containers.",
"title": "What privileges could be gained by an attacker who successfully exploited the vulnerability?"
},
{
"category": "faq",
"text": "A successful attack allows the container host to execute code in the targeted guest environment.",
"title": "According to the CVSS metric, successful exploitation could lead to a scope change (S:C). What does this mean for this vulnerability?"
},
{
"category": "faq",
"text": "To ensure secure and compliant use of Confidential virtual nodes on Azure Container Instances, customers must take the following actions:\nIf you are using Confidential virtual nodes, update to Helm chart version 1.3012.25080101 or later., Follow the deployment instructions provided in the https://github.com/microsoft/virtualnodesOnAzureContainerInstances repository.\nIf you are using Confidential ACI or Confidential virtual nodes, you must regenerate your Confidential Compute Environment (CCE) policy with a minimum infrastructure fragment SVN of 4.\nTo do this:\n*az extension update --name confcomShow more lines*\nAlternatively, you can manually set the infrastructure SVN using:\n*--infrastructure-svn 4*",
"title": "What actions need to be taken to mitigate this vulnerability?"
}
],
"product_status": {
"fixed": [
"12304"
],
"known_affected": [
"1"
]
},
"references": [
{
"category": "self",
"summary": "CVE-2025-59291 Confidential Azure Container Instances Elevation of Privilege Vulnerability - HTML",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-59291"
},
{
"category": "self",
"summary": "CVE-2025-59291 Confidential Azure Container Instances Elevation of Privilege Vulnerability - CSAF",
"url": "https://msrc.microsoft.com/csaf/advisories/2025/msrc_cve-2025-59291.json"
}
],
"scores": [
{
"cvss_v3": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 8.2,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"environmentalsScore": 0.0,
"exploitCodeMaturity": "UNPROVEN",
"integrityImpact": "HIGH",
"privilegesRequired": "HIGH",
"remediationLevel": "OFFICIAL_FIX",
"reportConfidence": "CONFIRMED",
"scope": "CHANGED",
"temporalScore": 7.1,
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C",
"version": "3.1"
},
"products": [
"1"
]
}
],
"threats": [
{
"category": "impact",
"details": "Elevation of Privilege"
},
{
"category": "exploit_status",
"details": "Publicly Disclosed:No;Exploited:No;Latest Software Release:Exploitation Less Likely"
}
],
"title": "Confidential Azure Container Instances Elevation of Privilege Vulnerability"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.