LiveActive security incident?Get immediate response
CVE Record

CVE-2026-47280: Azure Resource Manager Elevation of Privilege Vulnerability

Improper authentication in Azure Resource Manager (ARM) allows an unauthorized attacker to elevate privileges over a network.

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A flaw in Azure Resource Manager could let an unauthenticated remote attacker gain elevated privileges. Successful exploitation could expose, alter, or disrupt Azure resources across a security boundary. The supplied record rates it CVSS 10.0, but does not identify affected versions or deployment conditions.

Executive priority

Assign immediate ownership to the Azure security and operations teams. Require documented exposure assessment, vendor-guidance review, remediation confirmation, and monitoring. The maximum CVSS score warrants urgent action despite the absence of confirmed exploitation evidence.

Technical view

CVE-2026-47280 is an improper-authentication weakness (CWE-287) in Azure Resource Manager. Its CVSS vector indicates network reachability, low complexity, no required privileges or user interaction, changed scope, and high confidentiality, integrity, and availability impact. Specific affected versions and technical prerequisites are not provided.

Likely exposure

Organizations using Azure Resource Manager should treat possible exposure as broad until Microsoft defines the affected service scope. The source bundle lists no usable version range, so inventory or version checks alone cannot reliably exclude exposure.

Exploitation context

The supplied evidence does not establish active exploitation. The CVE is not listed as KEV in the bundle, and the CVSS exploit-maturity metric is unproven. These facts do not prove exploitation is absent; monitor Microsoft guidance for changes.

Researcher notes

The record supports a network-accessible authentication failure with changed scope and maximum impact metrics. It does not disclose affected versions, prerequisites, root cause details, indicators, or a specific fix. Validation should therefore remain advisory-led and avoid assuming every ARM deployment is exploitable.

Mitigation direction

  • Review the Microsoft advisory immediately for affected scope and prescribed remediation.
  • Apply or confirm Microsoft-required remediation as soon as applicable guidance is available.
  • Restrict unnecessary access to Azure management interfaces using supported organizational controls.
  • Monitor Azure Resource Manager activity for unexplained privilege, configuration, or resource changes.

Validation and detection

  • Map Azure tenants and subscriptions using Resource Manager against Microsoft's affected-scope guidance.
  • Confirm remediation status using the verification method specified by Microsoft.
  • Review relevant audit records for unexplained administrative or resource-management activity.
  • Reassess exposure whenever Microsoft updates the advisory or affected-product 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 · medium confidence lookup

CWE-287: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-47280 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
Critical
CVSS
10 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/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: yesTechnical Impact: total

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
10CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C3.96microsoft

Vulnerability scoring details

Base CVSS 3.1 score

10Critical
CVSS 3.1 vector shape for CVE-2026-47280Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/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 Resource Manager-Listed
Weakness

CWE details

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

CWE-287 · source CWE mapping

Improper Authentication

Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.