---
id: "CVE-2026-117472"
kind: "vulnerability"
aliases: ["CVE-2026-117472"]
title: "Psono Server: prefixed deployments let write-only API keys read secrets"
severity: "medium"
cvss: 4.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["api-keys", "package", "psono", "self-hosted"]
not_affected_if: ["default-config", "no-url-prefix", "no-write-only-api-keys"]
published_at: "2026-10-27T06:17:25+00:00"
first_seen_at: "2026-10-27T06:25:21+00:00"
updated_at: "2026-10-27T06:26:24+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-117472", "first_seen_at": "2026-10-27T06:25:21+00:00"}]
---

# Psono Server: prefixed deployments let write-only API keys read secrets

Psono Server versions 4.0.33 through 7.2.3 check the wrong path for the bulk-secret-read endpoint when URL_PREFIX is set, so the read-scope check is skipped. An authenticated attacker holding an API key with write but not read permission can retrieve encrypted secret data and nonces.

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

## How to check

- Check whether `URL_PREFIX` is set in the Psono server configuration.
- Check the installed Psono server version against the affected range `4.0.33` through `7.2.3`.
- Review API keys for any key that has write enabled and read disabled.

## Fix

- Upgrade Psono Server to a version later than `7.2.3`, per the advisory (fixed version unknown from sources).
- Rotate any API keys that were created with a read-disabled, write-enabled scope if exposure is suspected.

## Timeline

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

## From the sources

Psono Server CE && EE versions 4.0.33 through 7.2.3 compared the request path for the bulk-secret-read endpoint with a hard-coded unprefixed path. In deployments configured with URL_PREFIX, the comparison failed and the POST request was authorized using write scope instead of read scope. An authenticated remote attacker with an unusual read-disabled, write-enabled API key could therefore retrieve encrypted secret data and nonces through the prefixed bulk-secret-read endpoint despite lacking read permission. The default configuration without URL_PREFIX was not affected.

---

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