{"id":"CVE-2026-117472","aliases":["EUVD-2026-110606","GHSA-4hh2-mhpm-69h3"],"status":"published","title":"URL prefix handling permits API key read-scope bypass in Psono Server","description":"Psono Server CE \u0026\u0026 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.","severity":{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00323,"percentile":0.25641,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-863"],"published":"2026-10-27T05:56:16Z","modified":"2026-11-04T15:01:13Z","products":[{"vendor":"esaqa gmbh","product":"psono"}],"references":[{"url":"https://gitlab.com/esaqa/esaqa/security-advisories/-/blob/master/advisories/CVE-2026-117472.md","tags":["vendor-advisory","advisory"]},{"url":"https://gitlab.com/esaqa/psono/psono-server/-/blob/v7.2.3/psono/restapi/permissions.py","tags":["technical-description","article"]},{"url":"https://gitlab.com/esaqa/psono/psono-server/-/commit/5638d4be806af7d1dea03f7cad3927aa2bd19cf4","tags":["patch","fix"]},{"url":"https://gitlab.com/esaqa/psono/psono-server/-/releases/v7.2.4","tags":["release-notes","advisory"]},{"url":"https://gitlab.com/esaqa/psono/psono-server","tags":["product","package"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-117472","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-4hh2-mhpm-69h3"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/117xxx/CVE-2026-117472.json","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-117472","title":"URL prefix handling permits API key read-scope bypass in Psono Server","description":"Psono Server CE \u0026\u0026 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.","status":"published","published":"2026-10-27T05:56:16.775Z","modified":"2026-11-04T15:01:13.544Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-863"],"updated_at":"2026-11-04T16:33:47.459854Z"}],"euvd":[{"id":"EUVD-2026-110606","description":"Psono Server CE \u0026\u0026 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.","status":"published","published":"2026-10-27T05:56:16Z","modified":"2026-11-04T15:01:13Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium"}],"updated_at":"2026-11-04T16:10:35.925015Z"}],"ghsa":[{"id":"GHSA-4hh2-mhpm-69h3","title":"Psono Server CE \u0026\u0026 EE versions 4.0.33 through 7.2.3 compared the request path for the bulk-secret...","description":"Psono Server CE \u0026\u0026 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.","status":"published","published":"2026-10-27T06:31:23Z","modified":"2026-10-27T06:31:30Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium"}],"cwes":["CWE-863"],"updated_at":"2026-11-02T15:14:28.078787Z"}],"nvd":[{"id":"CVE-2026-117472","description":"Psono Server CE \u0026\u0026 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.","status":"published","published":"2026-10-27T06:17:25.153Z","modified":"2026-11-04T15:17:37.89Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-863"],"updated_at":"2026-11-04T18:06:23.753671Z"}],"osv":[{"id":"CVE-2026-117472","title":"URL prefix handling permits API key read-scope bypass in Psono Server","description":"Psono Server CE \u0026\u0026 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.","status":"published","published":"2026-10-27T05:56:16.775Z","modified":"2026-11-05T21:16:00.862623297Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium"}],"cwes":["CWE-863"],"updated_at":"2026-11-05T22:01:21.792402Z"}]}}