URL prefix handling permits API key read-scope bypass in Psono Server
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-863.
Summary
Psono Server CE and EE versions from 4.0.33 before 7.2.4 compare the request path for the bulk-secret-read endpoint against a hard-coded unprefixed path. When URL_PREFIX is configured, the comparison fails and the POST request is authorized with write scope instead of read scope (CWE-863). An authenticated remote attacker with an API key that has write enabled but read disabled can retrieve encrypted secret data and nonces through the prefixed endpoint. The default configuration without URL_PREFIX is not affected.
Written with Claude Haiku 5.5 from the sources below · 2026-11-04
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| esaqa GmbH | Psono | 4.0.33 to before 7.2.4 | 7.2.4 | Patch available | CNA |
- Psono Vendoresaqa GmbH Affected 4.0.33 to before 7.2.4 Fixed in 7.2.4 Patch available CNA
Remediation
Upgrade esaqa GmbH Psono to version 7.2.4, which fixes the issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-04
- Fix · CNA Psono (esaqa GmbH) Fixed in 7.2.4
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
esaqa Psono 7.2.4
5 records Highest priority Priority LOW 5 LOW
Other records, highest priority first
- TI-2026-81017 WebAuthn assertion replay permits second-factor bypass in Psono ServerPriority LOW 29
- TI-2026-81015 Device-code claim permits restricted token escalation in Psono ServerPriority LOW 29
- TI-2026-81018 User-controlled Duo host enables SSRF in Psono ServerPriority LOW 24
Timeline
- 2026-10-27 Threatist record created from CVE-2026-117472
- 2026-10-27 Alias added: GHSA-4hh2-mhpm-69h3
- 2026-11-04 CISA SSVC decision points changed
References
Patch 1
More esaqa GmbH vulnerabilities
- TI-2025-01732 Stored XSS in Psono-Client via Malicious Vault Entry URLs CVSS 4.0CRITICAL 9.3
- TI-2026-81017 WebAuthn assertion replay permits second-factor bypass in Psono Server CVSS 3.1MEDIUM 6.5
- TI-2026-81015 Device-code claim permits restricted token escalation in Psono Server CVSS 3.1MEDIUM 6.5
- TI-2026-81018 User-controlled Duo host enables SSRF in Psono Server CVSS 3.1MEDIUM 5.4
- TI-2026-81016 Psono file-transfer confusion allows unauthorized repository writes CVSS 3.1MEDIUM 5.4
Sources
- CVE-2026-117472 · CVE Program
- CVE-2026-117472 · NVD
- FIRST EPSS
- GHSA-4hh2-mhpm-69h3 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences