CVE-2026-26147
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 input validation in Azure Compute Gallery allows an authorized attacker to disclose information over a network.
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 confidenceImproper input validation in Azure Compute Gallery permits an authorized attacker to cause the service to disclose information over a network. The vulnerability stems from the service not properly validating input, allowing authorized users to potentially access information they should not see.
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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
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 usageIn the Azure Stack HCI environment, check if Azure Compute Gallery is enabled or deployed. Use the Azure Portal, Azure CLI (Get-AzGallery), or PowerShell (Get-AzStackHCI) to enumerate galleries. Look for any gallery resources in the subscription.Affected if Azure Compute Gallery resource exists in the subscription and is accessible to the user
-
Confirm Azure Stack HCI deploymentVerify the Azure Stack HCI cluster is present. Use PowerShell (Get-AzStackHCI) or check the Azure Portal for Azure Stack HCI resources. Note the cluster name and subscription.Affected if An Azure Stack HCI cluster is registered in the subscription, as all versions are affected
-
Review gallery permissions and role assignmentsIn Azure Portal, go to the Azure Compute Gallery resource, then Access control (IAM). Examine role assignments to see which users, groups, or service principals have access. Check for overly broad permissions such as Contributor or Owner roles on the gallery.Affected if Multiple users or groups have access beyond minimal required permissions, increasing the potential impact of the vulnerability
-
Audit recent gallery data accessIn Azure Portal, go to the gallery resource and review Activity Log for recent data access operations. Alternatively, enable Azure Resource Graph or Azure Sentinel to query gallery access patterns. Look for access to gallery images or shared images by users who should not normally access them.Affected if There are gallery access records from users accessing data outside their expected scope or from unexpected sources
If Azure Compute Gallery is deployed on Azure Stack HCI and the environment has multiple users with gallery access, the vulnerability is potentially exploitable since all Azure Stack HCI versions are affected.
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 dataOrganizations using Azure Compute Gallery should monitor for Microsoft security updates and apply patches when available. Review access controls and audit authorized user activities as a compensating control until the patch is deployed.
- Consultation4.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,336.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26147 — 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-26147 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