CVE-2026-35430
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 · uneditedAuthorization bypass through user-controlled key in Azure Privileged Identity Management (PIM) allows an authorized attacker to elevate privileges 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 confidenceThis is an authorization bypass vulnerability in Azure Privileged Identity Management (PIM) where user-controlled input is used to determine access control decisions (user-controlled key). An already authorized attacker can exploit this to elevate their privileges within the PIM system over the network.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Azure PIM is enabled in your tenantNavigate to Microsoft Entra admin center > Identity Governance > Privileged Identity Management, or run Get-AzureADMSPrivilegedRoleAssignment via MS Graph to verify PIM is provisionedAffected if PIM is active and managing role assignments - all versions of Azure PIM are vulnerable
-
Review recent role assignment changes for unauthorized elevationIn Azure Portal, go to PIM > Azure AD roles > Audit history, or query Microsoft Graph API: GET /privilegedAccess/azureAD/roleAssignmentAuditRecords - look for role assignments created outside normal business hours or by unexpected usersAffected if Suspicious role activations or assignments exist that were not initiated by authorized administrators
-
Check for unexpected permanent role assignmentsIn PIM dashboard, filter for role assignments where assignmentType equals 'Permanent' and were not explicitly created by your admin team - check Azure AD > Roles and administrators for assignments lacking proper justificationAffected if Permanent role assignments exist that were not properly approved through your change management process
-
Examine role activation patterns in audit logsQuery Microsoft Graph: GET /privilegedAccess/azureAD/roleEligibilityScheduleRequests or review PIM audit logs for role activations with unusual parameters, especially rapid successive activations of high-privilege rolesAffected if Role activations show abnormal patterns such as excessive activations or activations of roles outside normal scope
-
Correlate PIM activity with sign-in logsCross-reference Azure AD sign-in logs with PIM role activation events - look for activations from locations or devices inconsistent with the activating user's baselineAffected if Role activations originate from unfamiliar locations, anonymous proxies, or compromised devices
-
Check for role assignments with manipulated key parametersReview PIM role assignment API calls in Azure Monitor logs for requests containing unexpected or modified parameters - query Activity Log for 'Add member to role' operations with unusual timing or source attributesAffected if API audit records show role assignments with parameters that deviate from expected patterns or appear manipulated
Users are affected if Azure PIM is enabled and audit logs reveal unauthorized role assignments, unexpected privilege elevations, or suspicious role activation patterns that suggest the authorization bypass was exploited.
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 dataApply Microsoft security updates for Azure PIM as they become available. Review and audit PIM role assignments and privileged access after the patch is applied to ensure no unauthorized elevation occurred.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35430 — 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-35430 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