{"id":"CVE-2026-117468","kind":"vulnerability","aliases":["CVE-2026-117468"],"related":[],"title":"Psono Server: restricted API keys can claim full read-write sessions","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.","summary":"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.","severity":"medium","cvss":6.5,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["api-keys","other","password-manager","psono","self-hosted"],"not_affected_if":["default-config"],"how_to_check":"- Check the Psono Server version in use against the affected range 5.3.5 through 7.2.3\n- Review whether restricted API keys are issued to users or automation in your Psono deployment\n- 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)\n- Revoke restricted API keys and sessions that may have been abused until the upgrade is done","status":"open","published_at":"2026-10-27T06:17:24+00:00","first_seen_at":"2026-10-27T06:25:21+00:00","triaged_at":"2026-10-27T06:26:20+00:00","updated_at":"2026-10-27T06:26:20+00:00","category":"other","confidence":0.6,"triage":{"at":"2026-10-27T06:26:20Z","model":"claude-haiku-5-5","output":{"fix":"- Upgrade Psono Server to a version later than `7.2.3` (the exact fixed version is unknown from the sources)\n- Revoke restricted API keys and sessions that may have been abused until the upgrade is done","reach":"internet","title":"Psono Server: restricted API keys can claim full read-write sessions","impact":"medium","summary":"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.","category":"other","nicknames":[],"who_cares":["psono","self-hosted","password-manager","api-keys"],"confidence":0.6,"needs_auth":"yes","worst_case":"Attacker gains a full read-write session lasting up to 365 days","analyst_note":"Find the fixed Psono Server version and the exact device-code claim check in the NVD entry or Psono advisory.","how_to_check":"- Check the Psono Server version in use against the affected range 5.3.5 through 7.2.3\n- Review whether restricted API keys are issued to users or automation in your Psono deployment\n- Look for unexpected long-lived device-code sessions in Psono audit or session records (unknown if the sources give a specific location)","needs_analyst":true,"not_affected_if":["default-config"],"who_is_affected":"Self-hosted or managed Psono Server deployments running versions 5.3.5 through 7.2.3 that issue restricted API keys. The attacker needs an authenticated session derived from a restricted API key, and the flaw does not bypass two-factor authentication or directly disclose plaintext secrets. Deployments that do not use restricted API keys have a much smaller exposure.","user_interaction":"no","needs_special_setup":"unknown","severity_if_unknown":"medium"},"cost_usd":0.000658,"input_tokens":3366,"output_tokens":643,"severity_before":"medium"},"analyst_status":null,"analyst_note":null,"search":"'-117468':15A,18A '-2026':14A,17A '365':76B,132C '5.3.5':33B,81C '7.2.3':35B,83C 'api':4A,20B,54B,107C 'api-key':19B 'attack':50B,61B,103C,116C 'attacker-control':60B,115C 'authent':49B,101C,150C 'bypass':134C,146C 'check':38B 'claim':7A,47B,58B,96C,113C 'class':87C 'code':45B,64B,99C,119C 'control':62B,117C 'could':112C 'cve':13A,16A 'day':77B,133C 'deriv':110C 'devic':44B,63B,98C,118C 'direct':152C 'disclos':153C 'enforc':91C 'factor':149C 'full':8A,68B,123C 'get':66B 'hold':51B,104C 'host':29B 'key':5A,21B,55B,109C 'key-deriv':108C 'lifetim':141C 'manag':25B 'obtain':121C 'origin':136C 'password':24B 'password-manag':23B 'permiss':86C 'plaintext':154C 'psono':1A,26B,30B,78C 'read':10A,70B,125C 'read-writ':9A,69B,124C 'remot':102C 'restrict':3A,53B,106C,142C 'scope':41B,94C,139C 'secret':155C 'self':28B 'self-host':27B 'server':2A,31B,79C 'session':12A,56B,72B,111C,127C 'token':39B,92C,137C 'two':148C 'two-factor':147C 'use':84C 'valid':73B,128C 'version':32B,80C 'write':11A,40B,71B,93C,126C","nicknames":[],"mitigations":[],"who_affected":"Self-hosted or managed Psono Server deployments running versions 5.3.5 through 7.2.3 that issue restricted API keys. The attacker needs an authenticated session derived from a restricted API key, and the flaw does not bypass two-factor authentication or directly disclose plaintext secrets. Deployments that do not use restricted API keys have a much smaller exposure.","tier":"C","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-27T06:17:24+00:00","kev":null,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","cvss_by":"fdf66990-8419-4c8c-8848-ec15d75773b4","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-117468","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-117468","severity":null,"published_at":"2026-10-27T06:17:24+00:00","modified_at":"2026-10-27T06:17:24+00:00","first_seen_at":"2026-10-27T06:25:21+00:00","fetched_at":"2026-10-27T06:25:21+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}