# CVE-2026-117469: File-transfer type confusion permits unauthorized repository writes in Psono Server


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-jg7j-q6m4-7gq5

## What is CVE-2026-117469?

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

### Official description

Psono Server (CE & EE) versions 1.0.0 through 7.2.3 did not enforce the direction of file-transfer credentials on file-repository operations. An authenticated remote attacker with read-only access to a file could present a download transfer to the upload endpoint, obtain a signed upload URL for an attacker-selected object key, and append a chunk to the owner's file. Exploitation could upload or overwrite repository objects and consume storage, subject to transfer size, chunk-count, and lifetime limits.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-117469 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117469 is a medium-severity vulnerability in esaqa GmbH Psono, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117469 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-117469/ (Markdown: https://insights.sbomify.com/CVE-2026-117469/index.md)
```

## Sources

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

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