CVE-2026-117468: esaqa Psono · Improper Privilege Management
Affects esaqa PsonoSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 7.2.4 when convenient.
Data as of 27 Oct 2026, 05:57 UTC
- Patch
- Available – fixed in 7.2.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade esaqa Psono to 7.2.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| esaqa GmbHPsono | Affected
| Fixed in
|
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.
References
- gitlab.com/esaqa/psono/psono-server/-/blob/v7.2.3/psono/restapi/views/device_code_claim.py (opens in a new tab)
- gitlab.com/esaqa/psono/psono-server/-/commit/19ed5a192c704fece1645d946b6f4c36045bacbe (opens in a new tab)
- gitlab.com/esaqa/psono/psono-server/-/releases/v7.2.4 (opens in a new tab)
- gitlab.com/esaqa/psono/psono-server (opens in a new tab)