Security readout for executives and security teams
Plain-English summary
An already authorized Azure PIM user may bypass authorization controls and gain higher privileges remotely. Successful abuse could expose sensitive information, permit unauthorized changes, and disrupt services. The supplied record rates the issue 8.8 High, but does not identify affected versions or tenant configurations.
Executive priority
Treat as a high-priority identity-control issue because successful abuse could provide broad cloud privileges. Promptly establish tenant exposure, review privileged activity, and follow Microsoft's remediation guidance. Emergency incident response is not supported solely by the supplied exploitation evidence.
Technical view
CVE-2026-35430 is a CWE-639 authorization bypass involving a user-controlled key in Azure Privileged Identity Management. The CVSS vector indicates network access, low complexity, low existing privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure may exist where organizations use Azure PIM and an authorized, low-privileged attacker can reach the service. The source bundle provides no affected-version range, configuration prerequisites, or tenant-specific scope, so actual exposure cannot be determined from these sources alone.
Exploitation context
The supplied CVSS data describes remote, low-complexity exploitation requiring existing authorization and no victim interaction. The CVE is not listed as KEV in the bundle, and no cited source establishes active exploitation or public exploit availability.
Researcher notes
The record identifies CWE-639 and a user-controlled-key authorization bypass, but omits the vulnerable object type, affected versions, configuration conditions, and detailed remediation. The vector's E:U, RL:O, and RC:C fields indicate unproven exploit maturity, official remediation, and confirmed reporting; they do not prove exploitation.
Mitigation direction
- Review the Microsoft advisory for current affected-scope and remediation details.
- Apply Microsoft-provided updates or service-side remediation where the advisory directs.
- Restrict unnecessary PIM eligibility and assignments while exposure is assessed.
- Monitor privileged role activations and unexpected authorization changes.
Validation and detection
- Confirm whether the organization uses Azure Privileged Identity Management.
- Compare tenant configuration and service status against Microsoft's affected-scope guidance.
- Review PIM activations and role assignments for unexpected privilege elevations.
- Verify Microsoft-directed remediation is applied or service-side protection is confirmed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-639: 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 lookupPrivilege 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 lookupCVE-2026-35430 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C2.85.9microsoftVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Azure Privileged Identity Management (PIM) Elevation of Privilege VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.