How severe is CVE-2013-2132?

No CVSS score has been assigned to CVE-2013-2132 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-2132?

CVE-2013-2132 affects the following packages: pymongo (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2013-2132?

Update pymongo to 2.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2132 is resolved across your whole dependency graph.

How do I detect CVE-2013-2132 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pymongo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-2132 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2013-2132?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-2132 can be triaged on real exposure rather than presence alone.

Is CVE-2013-2132 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2013-2132, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-2132?

CVE-2013-2132 has an EPSS (Exploit Prediction Scoring System) score of 2.6%, placing it in the 85th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2013-2132 published, and has it been updated?

CVE-2013-2132 was published on August 15, 2013 and was last updated on August 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2013-2132 — pymongo

Fix: mongodb/mongo-python-driver@a060c15

CVE-2013-2132 is a security vulnerability in pymongo. 1 public exploit reference exists, so weaponization risk is real. A fix is available for pymongo — see the affected versions and patch details below.

Use of NullPointerException Catch to Detect NULL Pointer Dereference in Pymongo

Also known asGHSA-x33v-f3gp-gw2cPYSEC-2013-30

Published

Aug 15, 2013

Updated

Aug 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Sep 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐍pymongo

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

bson/_cbsonmodule.c in the mongo-python-driver (aka. pymongo) before 2.5.2, as used in MongoDB, allows context-dependent attackers to cause a denial of service (NULL pointer dereference and crash) via vectors related to decoding of an "invalid DBRef."

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`pymongo`	all versions	2.5.2`pip install --upgrade 'pymongo==2.5.2'`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

bson/_cbsonmodule.c in the mongo-python-driver (aka. pymongo) before 2.5…

github.comNVDOct 2018

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pymongo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pymongo to 2.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2132 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-2132 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2013-2132. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat Update Infrastructure 2.1.3 is now in Production 2 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Update Infrastructure Life Cycle:…

Product	Fixed in	Advisory
Red Hat Enterprise MRG 2	`mongodb-0:1.6.4-6.el6`	RHSA-2013:1170

Ubuntu

USN-1897-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-2132 in your dependencies?

O3 Security finds CVE-2013-2132 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works