Medium · CVSS 6.5CVE-2026-117468

Device-code claim permits restricted token escalation in Psono ServerCVE-2026-117468

Answer in brief

CVE-2026-117468 records a Medium severity (CVSS 6.5) vulnerability in Device-code claim permits restricted token escalation in Psono Server. The current sources do not mark it as known exploited. The current feed maps esaqa GmbH/Psono (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 27, 2026Updated Oct 27, 2026Source checked Oct 27, 2026First seen by HOL Oct 27, 2026Material review Oct 27, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.5
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps esaqa GmbH/Psono (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
esaqa GmbH/Psonogeneric	>=5.3.5 <7.2.4	7.2.4

Recommended response

Check inventory. Check lockfiles and deployed manifests for esaqa GmbH/Psono.
Review the reported fix. Source-reported solution: Upgrade to Psono Server 7.2.4 or later.

Evidence timeline and material changes

Published upstream
Oct 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 27, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.