CVE-2020-7610: All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data

Q: How do I fix CVE-2020-7610?

bson: upgrade to 1.1.4. Exact commands for each OS are on this page.

Q: Is CVE-2020-7610 being exploited?

CVE-2020-7610 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-2020-7610 affect?

CVE-2020-7610 affects bson. Severity is critical (CVSS 9.8). All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. The package will ignore an unknown value for an object's _bsotype, leading to cases where an object is serialized as a document rather than the intended

Q: How urgent is CVE-2020-7610?

Priority 60/100. Critical severity; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2020-7610 is a critical-severity flaw (CVSS 9.8) affecting bson. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. The package will ignore an unknown value for an object's _bsotype, leading to cases where an object is serialized as a document rather than the intended BSON type.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.3% (top 17%)
CISA exploited list	No
Weakness	CWE-502
Published	2020-03-30
Last modified	2026-06-17

Publisher (CNA): Snyk · Vendor: mongodb

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

Am I affected?

Timeline

2020-03-30 19:15 UTCPublished CVE record published
2026-06-17 03:25 UTCUpdated Record last modified

mongodb bson UPGRADE

Affected: >= 1.0.0 and < 1.1.4

Fixed in: 1.1.4

Safe to downgrade to: a release before 1.0.0

1. Check installed version

npm ls bson

2. UPGRADE to 1.1.4

npm install bson@">=1.1.4"

3. If no update is available yet, DOWNGRADE to a release before 1.0.0

npm view bson versions npm install bson@"<1.0.0"

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-2020-7610?

bson: upgrade to 1.1.4. Exact commands for each OS are on this page.

Is CVE-2020-7610 being exploited?

CVE-2020-7610 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-2020-7610 affect?

CVE-2020-7610 affects bson. Severity is critical (CVSS 9.8). All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. The package will ignore an unknown value for an object's _bsotype, leading to cases where an object is serialized as a document rather than the intended

How urgent is CVE-2020-7610?

Priority 60/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

MongoDB vulnerabilities

Related CVEs

CVE-2015-4412 CRITICAL 9.8 DOWNGRADE BSON injection vulnerability in the legal? function in BSON (bson-ruby) gem before 3.0.4 for Ruby allows remot
CVE-2015-4411 HIGH 7.5 UPGRADE MITIGATE The Moped::BSON::ObjecId.legal? method in mongodb/bson-ruby before 3.0.4 as used in rubygem-moped allows remot

References

← Back to latest CVEs