CVE
Devolutions PowerShell Universal privilege escalation to admin in app token management
Affects Devolutions PowerShell Universal 2026.3.4 and earlier, where an authenticated user with token creation or update permissions can escalate privileges to administrator. Fixed in 2026.3.5.
Written by a model from the sources below. Verify against them.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.3.5
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected product is PowerShell Universal 2026.3.4 and earlier. Attacker must hold token creation or update permissions (authenticated user). Revocation bypass applies to multi-node deployments.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.11% · 1st percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Devolutions PowerShell Universal contains an incorrect privilege assignment flaw in its app token management component. An authenticated user who already holds token creation or update permissions can send crafted app token requests to escalate their privileges to administrator, and can also reinstate a revoked app token in multi-node deployments.
Original description
Incorrect privilege assignment in the app token management component in Devolutions PowerShell Universal 2026.3.4 and earlier allows an authenticated user with token creation or update permissions to escalate privileges to administrator, and allows a revoked app token to be reinstated in multi-node deployments, via crafted app token requests that set an arbitrary role or revocation state.
Who should check
Teams running Devolutions PowerShell Universal 2026.3.4 and earlier, especially multi-node deployments where app tokens are used.
“Incorrect privilege assignment in the app token management component in Devolutions PowerShell Universal 2026.3.4 and earlier”
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 7.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected product is PowerShell Universal 2026.3.4 and earlier. Attacker must hold token creation or update permissions (authenticated user). Revocation bypass applies to multi-node deployments.Upgrade to a fixed version: 2026.3.5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-102632 (Incorrect privilege assignment in the app token management component in Devolutions PowerShell Universal 2026.3.4 and earlier allows an…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-102632 (entry last updated 2026-11-16):
Affected:
- Devolutions PowerShell Universal: fixed in 2026.3.5
Fixed versions: 2026.3.5.
Conditions (all must be true for the bug to be hit):
- Affected product is PowerShell Universal 2026.3.4 and earlier. (source: https://devolutions.net/security/advisories/DEVO-2026-0042/)
- Attacker must hold token creation or update permissions (authenticated user). (source: https://devolutions.net/security/advisories/DEVO-2026-0042/)
- Revocation bypass applies to multi-node deployments. (source: https://devolutions.net/security/advisories/DEVO-2026-0042/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-102632 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-102632 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://devolutions.net/security/advisories/DEVO-2026-0042/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-102632
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-102632"}.Public exploit activity
- EPSS: 0.11%
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Timeline
- CVE published
- First seen by cve.now3 days
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Devolutions PowerShell Universal
fixed in 2026.3.5
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-102632
Is CVE-2026-102632 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Incorrect privilege assignment in the app token management component lets an authenticated user with token creation or update permissions escalate privileges to administrator. In multi-node deployments, it can also reinstate a revoked app token.Source: devolutions.net
Which versions are affected by CVE-2026-102632?
PowerShell Universal: before 2026.3.5.Source: cve.now feed data
Am I affected, and how do I check?
PowerShell Universal 2026.3.4 and earlier are in scope. The revoked-token reinstatement applies specifically to multi-node deployments. To check the version, look at the installed PowerShell Universal version.Source: devolutions.net
How do I fix CVE-2026-102632?
Upgrade to PowerShell Universal 2026.3.5 or later.Source: devolutions.net