CVE-2025-59291
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 confidenceA path traversal vulnerability in Confidential Azure Container Instances allows an authenticated attacker to manipulate file paths and escape container isolation to elevate privileges locally on the host system.
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 use of Confidential Azure Container InstancesIn Azure Portal, navigate to Container Instances and check if the deployed containers are using Confidential Computing features (look for 'Confidential' container group type or Confidential VM sizes such as DCasv5 or DCesv5 series)Affected if The environment uses Confidential Azure Container Instances from Azure Compute Gallery
-
Verify Azure Compute Gallery usageRun 'az sig list' to list Azure Compute Galleries in the subscription, or check Resource Manager templates for references to '/subscriptions/{sub}/providers/Microsoft.Compute/galleries/'Affected if Azure Compute Gallery resources exist in the subscription and are used for container image storage or deployment
-
Check container deployment configurationReview container group definitions in Azure Resource Manager templates or via 'az container show' command, looking for image sources that reference Compute Gallery imagesAffected if Container images are sourced from Azure Compute Gallery custom images
-
Review container isolation settingsInspect container group properties for isolationType or securityPolicy fields; for Confidential Containers, look for 'Confidential' as the container group-os-type or security optionsAffected if Containers are configured with Confidential computing isolation enabled
The environment is affected if it uses Confidential Azure Container Instances deployed with custom images from Azure Compute Gallery, as all versions of Compute Gallery contain the path traversal flaw enabling container escape.
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 Azure security advisories for the official patch and ensure Confidential Container Instances are updated to the fixed version once released; verify container runtime configurations and network segmentation as temporary mitigations.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59291 — 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-59291 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