GHSA-r3xx-hw22-6h6w json
Writing to SFTP files resulting in sending out-of-bounds data to the server
published 3mo ago modified 3mo ago also JLSEC-2026-791
- cvss
- 3.9
- version 3.1, OSV
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### Impact
The `write(::SftpFile, ::DenseVector)` method assumed that the element type of the input vector had a size of 1 byte (e.g. `Int8`/`UInt8`), and used `length(data)` instead of `sizeof(data)` to get the number of bytes to send. If the input vector had a eltype with size more than 1 byte then this would result in some bytes *before* the vector in memory being sent (or a segfault).
Any user writing to an `SftpFile` is potentially impacted.
### Patches
The bug has been fixed in LibSSH v1.2.0.
### Workarounds
Ensure that all inputs to writing `SftpFile`'s are byte vectors.
Patch / fix
- julia LibSSH 1.1.0
Is GHSA-r3xx-hw22-6h6w in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| OSV | 3.1 | 3.9 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| julia | LibSSH | <1.1.0 |
1.1.0 |
Sources
- OSV JLSEC-2026-791
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.