---
id: "CVE-2026-117468"
kind: "vulnerability"
aliases: ["CVE-2026-117468"]
title: "Psono Server: restricted API keys can claim full read-write sessions"
severity: "medium"
cvss: 6.5
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["api-keys", "other", "password-manager", "psono", "self-hosted"]
not_affected_if: ["default-config"]
published_at: "2026-10-27T06:17:24+00:00"
first_seen_at: "2026-10-27T06:25:21+00:00"
updated_at: "2026-10-27T06:26:20+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-117468", "first_seen_at": "2026-10-27T06:25:21+00:00"}]
---

# Psono Server: restricted API keys can claim full read-write sessions

Psono Server versions 5.3.5 through 7.2.3 do not check token write scope when a device code is claimed. An authenticated attacker holding a restricted API key session can claim an attacker-controlled device code and get a full read-write session valid up to 365 days.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Psono Server version in use against the affected range 5.3.5 through 7.2.3
- Review whether restricted API keys are issued to users or automation in your Psono deployment
- Look for unexpected long-lived device-code sessions in Psono audit or session records (unknown if the sources give a specific location)

## Fix

- Upgrade Psono Server to a version later than `7.2.3` (the exact fixed version is unknown from the sources)
- Revoke restricted API keys and sessions that may have been abused until the upgrade is done

## Timeline

- 2026-10-27T06:25:21+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-117468

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_