CVE-2026-117468 json
Device-code claim permits restricted token escalation in Psono Server
published 13d ago modified 5d ago also EUVD-2026-110600
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- esaqa GmbH Psono 7.2.4
Is CVE-2026-117468 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5d ago
Exploit prediction
0.47% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected products
- esaqa GmbH Psono
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
gitlab.com
/esaqa/psono/psono-server/-/commit/19ed5a192c704fece1645d946b6f4c36045bacbe
patch
-
gitlab.com
/esaqa/esaqa/security-advisories/-/blob/master/advisories/CVE-2026-117468.md
vendor-advisory
-
gitlab.com
/esaqa/psono/psono-server/-/blob/v7.2.3/psono/restapi/views/device_code_claim.py
technical-description
-
gitlab.com
/esaqa/psono/psono-server/-/releases/v7.2.4
release-notes
-
gitlab.com
/esaqa/psono/psono-server
product
Sources
- CVE List CVE-2026-117468
- NVD CVE-2026-117468
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.