How severe is GHSA-65fr-j4p9-vc33?

GHSA-65fr-j4p9-vc33 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-65fr-j4p9-vc33?

GHSA-65fr-j4p9-vc33 affects the following packages: mongodb/mongodb (Packagist), mongodb/mongodb (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-65fr-j4p9-vc33?

Update mongodb/mongodb to 1.21.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-65fr-j4p9-vc33 is resolved across your whole dependency graph.

How do I detect GHSA-65fr-j4p9-vc33 in my Packagist dependencies?

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

How do I mitigate GHSA-65fr-j4p9-vc33 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.

Is GHSA-65fr-j4p9-vc33 actively exploited in the wild?

No public exploit code has been indexed for GHSA-65fr-j4p9-vc33 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-65fr-j4p9-vc33?

GHSA-65fr-j4p9-vc33 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th 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.

What type of vulnerability is GHSA-65fr-j4p9-vc33?

GHSA-65fr-j4p9-vc33 is classified as CWE-943 (CWE-943). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-65fr-j4p9-vc33 published, and has it been updated?

GHSA-65fr-j4p9-vc33 was published on September 8, 2026 and was last updated on September 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

mongodb: Reject "." and NUL bytes in database and collection namesGHSA-65fr-j4p9-vc33

HIGHFix: mongodb/mongo-php-library#1967

GHSA-65fr-j4p9-vc33 is a high-severity (CVSS 8.1) CWE-943 vulnerability in mongodb/mongodb. A fix is available for mongodb/mongodb — see the affected versions and patch details below.

Also known asCVE-2026-81525

Published

Sep 8, 2026

Updated

Sep 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-65fr-j4p9-vc33 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

🐘mongodb/mongodb🐘mongodb/mongodb

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

Description

The MongoDB client library for PHP does not sufficiently sanitize special elements in application-supplied namespace identifiers before using them to construct the target namespace for database operations. An application that incorporates untrusted text into these identifiers may have operations silently directed at a different storage location than the one the application intended.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`mongodb/mongodb`	all versions	1.21.4`composer require mongodb/mongodb:^1.21.4`
🐘Packagist	`mongodb/mongodb`	≥ 2.0.0&&< 2.4.1	2.4.1`composer require mongodb/mongodb:^2.4.1`

Affected Products

2 products · 4 configurations

Application

php drivermongodb

≥ 2.0.0 && < 2.4.1

range

Application

php librarymongodb

≥ 2.0.0 && < 2.4.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mongodb/mongodb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mongodb/mongodb to 1.21.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-65fr-j4p9-vc33 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.

Frequently Asked Questions

### Impact Passing untrusted input as part of a database or collection name may result in targeting a different database or collection than specified. ### Patches Fixed in PHP library 1.21.4 and 2.4.1. ### Workarounds Validate database and collection names prior to passing into APIs.