CVE-2026-117472
URL prefix handling permits API key read-scope bypass in Psono Server
- Medium 4.3
Description
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.
Key facts
- Published
- 27 Oct 2026
- Last changed
- 4 Nov 2026
- Assigned by
- esaqa
- EPSS
- 0.323% likely to be exploited in the next 30 days, higher than 25.72% of CVEs (scores for 17 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 4.3CVSS 3.1, Mediumfrom the CNA (esaqa)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
What to do
- Upgrade to Psono Server 7.2.4 or later.CNA solution statement
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
A write-only API key could read encrypted secret records through the bulk-secret-read endpoint despite having its read scope disabled. (CNA impact statement)
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| esaqa GmbH | Psono |
|
Timeline
- 29 Jul 2026 Vulnerability reported to vendor
- 30 Jul 2026 Vendor fix implemented
- 30 Jul 2026 Psono CE & EE Server 7.2.4 released
- 27 Oct 2026 Published