CVE-2026-82053: A security issue exists in MongoDB's LDAP authorization integration where pooled LDAP connections can retain stale authentication identities after user authentication under certain configurations.

High CVSS 8.1

CVE id
CVE-2026-82053
Published
Last modified

Affected packages

PackageAffected versionsFixed in
MongoDB
Runtimes and servers
>= 7.0.0, < 7.0.41
>= 8.0.0, < 8.0.30
>= 8.2.0, <= 8.2.12
>= 8.3.0, < 8.3.9
7.0.41, 8.0.30, 8.3.9

How to fix it

Upgrade MongoDB to the fixed release of the line you run: 7.0.41, 8.0.30, 8.3.9.

mongod --version
  • Install the patched MongoDB release of your series (the mongo image tag or the mongodb-org packages); on Atlas, MongoDB patches the servers.

A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.

Details

A security issue exists in MongoDB's LDAP authorization integration where pooled LDAP connections can retain stale authentication identities after user authentication under certain configurations. Subsequent authorization queries may execute under an unintended LDAP identity rather than the expected one. This can result in incorrect role assignments based on the LDAP directory's access control configuration, potentially allowing an authenticated user to acquire elevated privileges that were not intended by the deployment's authorization policy.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.