Psono Server CE 和 EE 版本 4.0.33 至 7.2.3 在批量秘密读取(bulk-secret-read)端点中,将请求路径与一个硬编码的、未添加前缀的路径进行了比较。在配置了 URL_PREFIX 的部署环境中,该比较会失败,导致 POST 请求错误地使用了写权限(write scope)而非读权限(read scope)进行授权。因此,拥有非常规的“禁用读取、启用写入”API 密钥的已认证远程攻击者,即使不具备读取权限,仍可通过带前缀的批量秘密读取端点获取加密的秘密数据及随机数(nonce
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| esaqa GmbH | Psono | 4.0.33 ~ 7.2.4 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-117468 | 6.5 MEDIUM | Device-code claim permits restricted token escalation in Psono Server |
| CVE-2026-117470 | 6.5 MEDIUM | WebAuthn assertion replay permits second-factor bypass in Psono Server |
| CVE-2026-117471 | 5.4 MEDIUM | User-controlled Duo host permits authenticated SSRF in Psono Server |
| CVE-2026-117469 | 5.4 MEDIUM | File-transfer type confusion permits unauthorized repository writes in Psono Server |