CVE-2021-38599: WAL-G before 1.1, when a non-libsodium build (e.g., one of the official binary releases published as GitHub Re

Q: How do I fix CVE-2021-38599?

wal-g: upgrade to 1.1. Exact commands for each OS are on this page.

Q: Is CVE-2021-38599 being exploited?

CVE-2021-38599 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2021-38599 affect?

CVE-2021-38599 affects wal-g. Severity is high (CVSS 7.5). WAL-G before 1.1, when a non-libsodium build (e.g., one of the official binary releases published as GitHub Releases) is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Leas

Q: How urgent is CVE-2021-38599?

Priority 46/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2021-38599 is a high-severity flaw (CVSS 7.5) affecting wal-g. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

WAL-G before 1.1, when a non-libsodium build (e.g., one of the official binary releases published as GitHub Releases) is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because "the user likely wanted to encrypt all file activity."

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.8% (top 42%)
CISA exploited list	No
Weakness	CWE-754
Published	2021-08-12
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: wal-g project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-08-12 16:15 UTCPublished CVE record published
2026-06-17 04:02 UTCUpdated Record last modified

wal-g project wal-g UPGRADE

Affected: < 1.1

Fixed in: 1.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wal-g || rpm -q wal-g || wal-g --version

2. UPGRADE to 1.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wal-g

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wal-g

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2021-38599?

wal-g: upgrade to 1.1. Exact commands for each OS are on this page.

Is CVE-2021-38599 being exploited?

CVE-2021-38599 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2021-38599 affect?

CVE-2021-38599 affects wal-g. Severity is high (CVSS 7.5). WAL-G before 1.1, when a non-libsodium build (e.g., one of the official binary releases published as GitHub Releases) is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Leas

How urgent is CVE-2021-38599?

Priority 46/100. High severity; Remotely exploitable, no login, no user action

Software pages

GitHub vulnerabilities

References

← Back to latest CVEs