LiveActive security incident?Get immediate response
CVE Record

CVE-2026-26147: Azure Stack HCI Information Disclosure Vulnerability

Improper input validation in Azure Compute Gallery allows an authorized attacker to disclose information over a network.

HighCVSS 7.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

An authorized, low-privilege attacker could exploit improper input validation to obtain sensitive information remotely. The issue is rated high because disclosure may cross a security boundary and significantly affect confidentiality, although the supplied sources indicate no integrity or availability impact.

Executive priority

Prioritize prompt exposure confirmation and remediation because successful exploitation could disclose sensitive information across a security boundary. Immediate emergency action is not supported by the supplied evidence, but low attack complexity and remote reachability justify expedited handling where affected services are present.

Technical view

CVE-2026-26147 is a CWE-20 improper-input-validation vulnerability described in Azure Compute Gallery and associated with Azure Stack HCI. CVSS 3.1 is 7.7: network-accessible, low complexity, low privileges, no user interaction, changed scope, and high confidentiality impact. Supplied version details are incomplete.

Likely exposure

Potential exposure applies to organizations using affected Azure Stack HCI or related Azure Compute Gallery functionality. Exact vulnerable versions, configurations, and prerequisites are not identified in the supplied bundle, so exposure must be confirmed against Microsoft's advisory and asset inventory.

Exploitation context

The attacker must already be authorized but needs only low privileges. Exploitation is remotely reachable, low complexity, and requires no user interaction. The CVSS exploit-maturity value is unproven, and the CVE is not listed as KEV in the supplied evidence; active exploitation is therefore not established.

Researcher notes

The source bundle names Azure Stack HCI as affected while describing the flaw in Azure Compute Gallery; their precise component relationship is not explained. No affected version range, disclosed information type, technical root-cause detail, or exploitation evidence is supplied. Researchers should avoid inferring broader Azure exposure.

Mitigation direction

  • Review the Microsoft advisory for applicable versions, updates, and deployment requirements.
  • Apply Microsoft-provided security updates to confirmed affected systems using normal change controls.
  • Restrict low-privilege access to Azure Compute Gallery functionality where operationally feasible.
  • Monitor Microsoft guidance for revised affected-version or mitigation details.

Validation and detection

  • Inventory Azure Stack HCI deployments and their Azure Compute Gallery dependencies.
  • Compare installed versions and update status with Microsoft's CVE advisory.
  • Confirm security updates were successfully applied across every affected deployment.
  • Review available audit records for unusual authorized access to gallery resources.
  • Reassess exposure if Microsoft publishes configuration-specific applicability details.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-26147 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.7CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:U/RL:O/RC:C3.14microsoft

Vulnerability scoring details

Base CVSS 3.1 score

7.7High
CVSS 3.1 vector shape for CVE-2026-26147Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftAzure Stack HCI-Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.