CVE-2024-8013: A bug in query analysis of certain complex self-referential $lookup subpipelines may result in literal values

Routine

LOW 2.2UPGRADEUPGRADE

CVE-2024-8013 is a low-severity flaw (CVSS 2.2) affecting mongo crypt v1.so, mongocryptd. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A bug in query analysis of certain complex self-referential $lookup subpipelines may result in literal values in expressions for encrypted fields to be sent to the server as plaintext instead of ciphertext. Should this occur, no documents would be returned or written. This issue affects mongocryptd binary (v5.0 versions prior to 5.0.29, v6.0 versions prior to 6.0.17, v7.0 versions prior to 7.0.12 and v7.3 versions prior to 7.3.4) and mongo_crypt_

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	2.2 (Low)
Attack vector	Local
Attack complexity	High
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.1% (top 98%)
CISA exploited list	No
Weakness	CWE-319
Published	2024-10-28
Last modified	2026-06-17

Publisher (CNA): MongoDB, Inc. · Vendor: mongodb

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

Am I affected?

Timeline

2024-10-28 13:15 UTCPublished CVE record published
2026-06-17 08:21 UTCUpdated Record last modified

mongodb mongo crypt v1.so UPGRADE

Affected: >= 6.0.0 and < 6.0.17 · >= 7.0.0 and < 7.0.12 · >= 7.3.0 and < 7.3.4

Fixed in: 6.0.17, 7.0.12, 7.3.4

Safe to downgrade to: a release before 6.0.0

1. Check installed version

apt-cache policy mongo-crypt-v1.so || rpm -q mongo-crypt-v1.so || mongo-crypt-v1.so --version

2. UPGRADE to 6.0.17 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade mongo-crypt-v1.so

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade mongo-crypt-v1.so

Note

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

3. If no update is available yet, DOWNGRADE to a release before 6.0.0 (Debian / Ubuntu)

apt-cache madison mongo-crypt-v1.so sudo apt install mongo-crypt-v1.so=<VERSION_BEFORE_6.0.0> sudo apt-mark hold mongo-crypt-v1.so

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list mongo-crypt-v1.so sudo dnf downgrade mongo-crypt-v1.so-<VERSION_BEFORE_6.0.0> sudo dnf versionlock add mongo-crypt-v1.so

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

mongodb mongocryptd UPGRADE

Affected: >= 5.0.0 and < 5.0.29 · >= 6.0.0 and < 6.0.17 · >= 7.0.0 and < 7.0.12 · >= 7.3.0 and < 7.3.4

Fixed in: 5.0.29, 6.0.17, 7.0.12, 7.3.4

Safe to downgrade to: a release before 5.0.0

1. Check installed version

apt-cache policy mongocryptd || rpm -q mongocryptd || mongocryptd --version

2. UPGRADE to 5.0.29 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade mongocryptd

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade mongocryptd

Note

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

3. If no update is available yet, DOWNGRADE to a release before 5.0.0 (Debian / Ubuntu)

apt-cache madison mongocryptd sudo apt install mongocryptd=<VERSION_BEFORE_5.0.0> sudo apt-mark hold mongocryptd

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list mongocryptd sudo dnf downgrade mongocryptd-<VERSION_BEFORE_5.0.0> sudo dnf versionlock add mongocryptd

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-2024-8013?

mongo crypt v1.so: upgrade to 6.0.17, 7.0.12, 7.3.4; mongocryptd: upgrade to 5.0.29, 6.0.17, 7.0.12, 7.3.4. Exact commands for each OS are on this page.

Is CVE-2024-8013 being exploited?

CVE-2024-8013 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-2024-8013 affect?

CVE-2024-8013 affects mongo crypt v1.so, mongocryptd. Severity is low (CVSS 2.2). A bug in query analysis of certain complex self-referential $lookup subpipelines may result in literal values in expressions for encrypted fields to be sent to the server as plaintext instead of ciphertext. Should this occur, no documents w

How urgent is CVE-2024-8013?

Priority 8/100. No elevated risk signals yet.

Software pages

MongoDB vulnerabilities

References

← Back to latest CVEs