File-transfer type confusion permits unauthorized repository writes in Psono Server
Impact
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.
Source excerpt · esaqaWhat to do
Upgrade to Psono Server 7.2.4 or later.
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
esaqa GmbH · Psono
Other versions: unaffected
| Version / range | Source status |
|---|---|
| 1.0.0 to before 7.2.4 | affected |
Original source 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.
References
- Security advisory gitlab.com/esaqa/esaqa/security-advisories/-/blob/master/advisories/CVE-2026-117469.md
- Source reference gitlab.com/esaqa/psono/psono-server/-/blob/v7.2.3/psono/restapi/serializers/file_repository_upload.py
- Patch gitlab.com/esaqa/psono/psono-server/-/commit/64753b19bd8d03cfbed20db575f4dccb220d9ca4
- Release notes gitlab.com/esaqa/psono/psono-server/-/releases/v7.2.4
- Source reference gitlab.com/esaqa/psono/psono-server