CVE-2026-117469 json
File-transfer type confusion permits unauthorized repository writes in Psono Server
published 13d ago modified 5d ago also EUVD-2026-110603
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- esaqa GmbH Psono 7.2.4
Is CVE-2026-117469 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5d ago
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L |
Affected products
- esaqa GmbH Psono
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
-
gitlab.com
/esaqa/psono/psono-server/-/commit/64753b19bd8d03cfbed20db575f4dccb220d9ca4
patch
-
gitlab.com
/esaqa/esaqa/security-advisories/-/blob/master/advisories/CVE-2026-117469.md
vendor-advisory
-
gitlab.com
/esaqa/psono/psono-server/-/blob/v7.2.3/psono/restapi/serializers/file_repository_upload.py
technical-description
-
gitlab.com
/esaqa/psono/psono-server/-/releases/v7.2.4
release-notes
-
gitlab.com
/esaqa/psono/psono-server
product
Sources
- CVE List CVE-2026-117469
- NVD CVE-2026-117469
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.