Skip to main content
VulnerabilityPublished Updated

CVE-2024-5629: Mongo orchestration · PyMongo Out-of-bounds Read in the bson module

Affects mongo-orchestrationSource GCVE Database

0
Compare

Not known to be exploited · CVSS 4.7 Medium : upgrade to 0.8.0_4 when convenient.

Data as of 30 Oct 2026, 07:00 UTC

CVSS 3.1 base score
4.7Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.8.0_4
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade mongo-orchestration to 0.8.0_4.

Affected software

ProductAffectedFixed in
Homebrewmongo-orchestrationpkg:brew/mongo-orchestrationOther threatsAffected
  • >=0.5 <0.8.0_4
Fixed in
  • 0.8.0_4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade pymongo to version 4.6.3 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated.

Description

An out-of-bounds read vulnerability exists in the bson module of pymongo versions before 4.6.3. This flaw allows an attacker to craft a payload that forces the parser to deserialize unmanaged memory, potentially causing exceptions when parsing non-printable UTF-8 bytes. The issue is fixed in pymongo version 4.6.3.

References

Community reviews

Loading reviews…