CVE-2026-117468

Device-code claim permits restricted token escalation in Psono Server

Published Oct 27, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Psono Server versions 5.3.5 through 7.2.3 contained a flaw in the device-code claim process that allowed an authenticated remote attacker with a restricted API key to claim an attacker‑controlled device code. The resulting session granted unrestricted read‑write privileges for up to one year, effectively bypassing the original token’s scope and lifetime limitations. The vulnerability did not remove the requirement for two‑factor authentication or expose plaintext secrets, but it did provide a persistent elevation of privileges for the attacker.

Affected Systems

The affected product is Psono Server from esaqa GmbH. Any deployment running a version between 5.3.5 and 7.2.3 inclusive could exploit the flaw.

Risk and Exploitability

The CVSS score of 6.5 indicates a medium severity. EPSS data are not available and the vulnerability is not listed in the CISA KEV catalog, so publicly known exploitation is not yet confirmed. The attack requires remote access to a Psono Server instance, possession of a restricted API key, and the ability to claim a device code. The likely attack vector is remote service abuse through the exposed API; this inference is based on the fact that the attacker must interact with the server over its REST interface. Because the flaw permits persistent full‑access sessions, the risk to confidentiality and integrity is high if the attacker succeeds. Security teams should treat this as a significant threat to any system that still runs an affected version.

Remediation

Vendor Solution

Upgrade to Psono Server 7.2.4 or later.


OpenCVE Recommended Actions

  • Upgrade Psono Server to version 7.2.4 or later as published by esaqa GmbH
  • Revoke any compromised or unnecessary API keys that might have been used to obtain restricted tokens
  • Implement least‑privilege controls on API access and monitor for unusual device‑code claim activity

Generated by OpenCVE AI on October 27, 2026 at 08:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Esaqa
Esaqa psono
Vendors & Products Esaqa
Esaqa psono
Type Values Removed Values Added
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.
Title Device-code claim permits restricted token escalation in Psono Server
Weaknesses CWE-269
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N'}

Weaknesses
  • CWE-269

    Improper Privilege Management

Sources

Status
PUBLISHED
Assigner
esaqa
Published
Updated
Nov 4, 2026, 3:01 PM
Reserved
Oct 27, 2026, 5:33 AM
Status
Deferred
Published
Oct 27, 2026, 6:17 AM
Modified
Nov 4, 2026, 3:17 PM