Skip to content
Fencer Vulns
high 8.1

CVE-2018-16790 json

_bson_iter_next_internal in bson-iter.c in libbson 1.12.0, as used in MongoDB mongo-c-driver and other products, has a heap-based buffer ov…

published 2018-09-10 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-8590

cvss
8.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

_bson_iter_next_internal in bson-iter.c in libbson 1.12.0, as used in MongoDB mongo-c-driver and other products, has a heap-based buffer over-read via a crafted bson buffer.

Patch / fix

  • mongo-c-driver Debian 14, Debian 13, Debian 12 1.13.0-1
  • libbson-xs-perl Debian 12 0.8.4-2+deb12u1

debian advisories DEBIAN-CVE-2018-16790

  • libbson Ubuntu Pro 16.04 LTS 1.3.1-1ubuntu0.1~esm1
  • libbson Ubuntu Pro 18.04 LTS 1.9.2-1ubuntu0.1~esm2

ubuntu advisories UBUNTU-CVE-2018-16790

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-16790 updated cvss 6.3

libbson: Heap-based buffer over-read in _bson_iter_next_internal in bson-iter.c

  • Red Hat Software Collections rh-mongodb34-libbson, rh-mongodb36-libbson
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.13% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 8.1 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:N/A:P

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.