CVE-2026-21522
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 · uneditedImproper neutralization of special elements used in a command ('command injection') 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 confidenceCommand injection vulnerability in Azure Compute Gallery allows an authorized attacker to inject arbitrary commands through improper neutralization of special elements, leading to local privilege escalation. The vulnerability affects the Azure Compute Gallery service component and requires an attacker to have some level of authorized access.
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 data< 1.2.8CVSS 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 usageReview your Azure subscription resources to determine if Azure Compute Gallery is deployed. Use Azure Resource Graph, Azure Portal resource lists, or Azure CLI command: az resource list --query "[?type=='Microsoft.Compute/galleries']"Affected if Azure Compute Gallery resources exist in the subscription
-
Locate Microsoft Confcom componentMicrosoft Confcom is the affected service component. Check for Confcom-related processes, services, or dependencies within your Azure Compute Gallery environment. Consult Azure service documentation for component identification methods.Affected if Microsoft Confcom is present in the environment
-
Determine installed Confcom versionCompare your Microsoft Confcom version against the affected range. Use Azure diagnostic commands, service configuration exports, or Azure Monitor logs to retrieve the version number. Common methods include checking service manifests, runtime logs, or Azure Arc-enabled server inventories if applicable.Affected if Installed version is below 1.2.8
-
Verify authorized user access to Compute GalleryReview Azure role-based access control (RBAC) assignments on the affected Azure Compute Gallery resources. Check for users with roles that grant write or contributor-level permissions. Use Azure CLI: az role assignment list --scope "/subscriptions/<sub-id>/resourceGroups/<rg>/providers/Microsoft.Compute/galleries/<gallery-name>"Affected if Multiple authorized users have elevated permissions to the Compute Gallery resource
-
Audit command execution capabilitiesExamine whether the Compute Gallery has custom image definitions or run commands enabled that could accept user-supplied input. Review any custom script extensions or image build processes that interface with Confcom.Affected if Custom image workflows or command injection points are accessible to authorized users
You are affected if Azure Compute Gallery is in use, Microsoft Confcom is present, its version is below 1.2.8, and authorized users have elevated access to trigger the command injection pathway.
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 data1.2.8
Monitor Azure security advisories for the official Microsoft patch; review access controls and audit authorized user permissions to the Azure Compute Gallery resource until a patch is applied.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21522 — 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-21522 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