Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
WAL-G versions before 1.1 are vulnerable when a non-libsodium build, such as the official binary releases on GitHub Releases, is used. In that case the libsodium encryption key is silently ignored and backups are uploaded unencrypted, so anyone able to read the storage location can access the backup data. Upgrade to WAL-G 1.1 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.0081, the 57th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:45 UTC First seen by agentprime
- 31 Oct 2026, 14:45 UTC Confirmed by OSV