CVE-2026-117468
Device-code claim permits restricted token escalation in Psono Server
- Medium 6.5
Description
Psono Server versions 5.3.5 through 7.2.3 used a permission class that did not enforce token write scope when claiming a device code. An authenticated remote attacker holding a restricted API key-derived session could claim an attacker-controlled device code and obtain a full read-write session valid for up to 365 days, bypassing the original token's scope and lifetime restrictions. This did not bypass two-factor authentication or directly disclose plaintext secrets.
Key facts
- Published
- 27 Oct 2026
- Last changed
- 4 Nov 2026
- Assigned by
- esaqa
- EPSS
- 0.468% likely to be exploited in the next 30 days, higher than 41.047% of CVEs (scores for 17 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 6.5CVSS 3.1, Mediumfrom the CNA (esaqa)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
What to do
- Upgrade to Psono Server 7.2.4 or later.CNA solution statement
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
A restricted, short-lived API key session could be escalated to a full read-write session lasting up to 365 days, enabling unauthorized modification of encrypted secrets and shares. (CNA impact statement)
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| esaqa GmbH | Psono |
|
Timeline
- 29 Jul 2026 Vulnerability reported to vendor
- 30 Jul 2026 Vendor fix implemented
- 30 Jul 2026 Psono CE & EE Server 7.2.4 released
- 27 Oct 2026 Published