CVE-2025-59292
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedExternal control of file name or path in Confidential Azure Container Instances allows an authorized attacker to elevate privileges locally.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a path traversal vulnerability in Azure's Confidential Container Instances where an authorized attacker can manipulate file paths to escape container boundaries and elevate privileges locally. The vulnerability stems from insufficient validation of file names/paths passed to file operations within the confidential computing environment.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Azure Confidential Container Instances are in useCheck your Azure resource inventory or deployment scripts for instances of type Microsoft.ContainerInstance/containerGroups with 'confidentialComputing' or 'Confidential' sku/tierAffected if Resources exist using Azure Confidential Container Instances service
-
Verify Azure Compute Gallery image sourceReview container image references in your deployment configurations (YAML, Terraform, ARM templates) to determine if images are sourced from Azure Compute Gallery (formerly Shared Image Gallery)Affected if Container images are pulled from Azure Compute Gallery
-
Inspect file mount configurationsExamine container deployment configurations for any hostPath mounts, volume mounts, or emptyDir configurations that expose host filesystem pathsAffected if Container has file mounts that could be targeted for path traversal
-
Review custom path bindingsCheck for any custom volume or path bindings in container specifications, particularly those allowing host path access or custom file operationsAffected if Custom path bindings that accept user-controlled file paths are configured
-
Audit file operation loggingReview container audit logs or Azure Container Instances diagnostic logs for any anomalous file access patterns or path traversal attemptsAffected if Suspicious path traversal patterns appear in file operation logs
You are affected if you are running Azure Confidential Container Instances with images from Azure Compute Gallery and have file mount configurations that could be manipulated through insufficient path validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataMonitor Microsoft's security advisory for the patch release; once available, redeploy Confidential Azure Container Instances to receive the updated infrastructure. Review container deployment configurations for any suspicious file mount points or path references.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59292 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59292 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data