CVE-2026-23651
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 · uneditedPermissive regular expression in Azure Compute Gallery 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 permissive regular expression in Azure Compute Gallery allows an authorized attacker to bypass intended access controls through crafted input, enabling local privilege escalation. The regex likely fails to properly validate or sanitize input fields, allowing injection of elevated privileges or execution with higher permissions than intended for the authenticated user.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/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 Azure Compute Gallery usageRun 'az resource list --resource-type Microsoft.Compute/galleries' to list all Azure Compute Gallery resources in your subscriptionAffected if Any Azure Compute Gallery resources exist in the subscription
-
Detect Aci Confidential Containers deploymentsRun 'az container list --output table' and review output for containers with 'Confidential' in the SKU or configurationAffected if Any Aci Confidential Containers are running or deployed
-
Check for compute gallery image definitionsRun 'az sig definition list --gallery-name <gallery-name>' for each gallery found, to identify image definitions that may be used by Aci Confidential ContainersAffected if Image definitions exist and are referenced by confidential container deployments
-
Review role assignments on compute galleriesRun 'az role assignment list --assignee <user-or-spn> --scope <gallery-resource-id>' to enumerate who has access to the galleriesAffected if Multiple users or service principals have elevated permissions on the galleries (indicates potential target for privilege escalation)
-
Inspect container orchestration configsReview any YAML or ARM templates used to deploy Aci Confidential Containers, checking for custom parameters that pass through to gallery image referencesAffected if Custom parameters or user inputs are passed to image references without validation
If you have any Azure Compute Gallery resources being used by Aci Confidential Containers, your environment is affected since all versions are vulnerable to regex-based privilege escalation.
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 dataAwait the official Microsoft patch for Azure Compute Gallery; in the meantime, limit user permissions to the minimum required and monitor for unusual privilege escalation attempts. Validate that any Azure role assignments follow least-privilege principles.
- Consultation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23651 — 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-2026-23651 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