# CVE-2026-117472: URL prefix handling permits API key read-scope bypass in Psono Server


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-4hh2-mhpm-69h3

## What is CVE-2026-117472?

CVE-2026-117472 is a medium-severity vulnerability in esaqa GmbH Psono, published on 27 Oct 2026. 

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-117472?


## How do I fix CVE-2026-117472?

No fix has been published for CVE-2026-117472 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-117472 being exploited?

There is no known exploitation of CVE-2026-117472 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-117472 and fix it if it is affected.

What it is: CVE-2026-117472 is a medium-severity vulnerability in esaqa GmbH Psono, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117472 in the wild and no public exploit code.

Affected product: esaqa GmbH Psono. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-117472/ (Markdown: https://insights.sbomify.com/CVE-2026-117472/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-117472
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-117472
- OSV: https://osv.dev/vulnerability/CVE-2026-117472

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-117472/
Summaries are generated and may contain mistakes; the official description above is the record.