How severe is GHSA-rghw-6px2-fgwc?

GHSA-rghw-6px2-fgwc has a CVSS score of 6.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-rghw-6px2-fgwc?

GHSA-rghw-6px2-fgwc affects the following packages: org.mongodb:mongodb-driver (Maven), org.mongodb:mongodb-driver (Maven), org.mongodb:mongodb-driver-sync (Maven), org.mongodb:mongodb-driver-sync (Maven), org.mongodb:mongodb-driver-sync (Maven), org.mongodb:mongo-java-driver (Maven), org.mongodb:mongo-java-driver (Maven), org.mongodb:mongodb-driver-legacy (Maven), and 6 more. Ecosystems affected: Maven.

How do I fix GHSA-rghw-6px2-fgwc?

Update org.mongodb:mongodb-driver to 3.11.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rghw-6px2-fgwc is resolved across your whole dependency graph.

How do I detect GHSA-rghw-6px2-fgwc in my Maven dependencies?

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

How do I mitigate GHSA-rghw-6px2-fgwc 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-rghw-6px2-fgwc actively exploited in the wild?

No public exploit code has been indexed for GHSA-rghw-6px2-fgwc 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-rghw-6px2-fgwc?

GHSA-rghw-6px2-fgwc has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 38th 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-rghw-6px2-fgwc?

GHSA-rghw-6px2-fgwc is classified as CWE-295 (CWE-295). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rghw-6px2-fgwc published, and has it been updated?

GHSA-rghw-6px2-fgwc was published on May 24, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

Improper Certificate Validation in MongoDBGHSA-rghw-6px2-fgwc

MEDIUM

GHSA-rghw-6px2-fgwc is a medium-severity (CVSS 6.8) CWE-295 vulnerability in org.mongodb:mongodb-driver. A fix is available for org.mongodb:mongodb-driver — see the affected versions and patch details below.

Also known asCVE-2021-20328

Published

May 24, 2022

Updated

Feb 16, 2024

Affected

14 pkgs

Patched

14 / 14

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rghw-6px2-fgwc.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

14 pkgs affected

☕org.mongodb:mongodb-driver☕org.mongodb:mongodb-driver☕org.mongodb:mongodb-driver-sync☕org.mongodb:mongodb-driver-sync☕org.mongodb:mongodb-driver-sync☕org.mongodb:mongo-java-driver☕org.mongodb:mongo-java-driver☕org.mongodb:mongodb-driver-legacy+6 more

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

Description

Specific versions of the Java driver that support client-side field level encryption (CSFLE) fail to perform correct host name verification on the KMS server’s certificate. This vulnerability in combination with a privileged network position active MITM attack could result in interception of traffic between the Java driver and the KMS service rendering Field Level Encryption ineffective. This issue was discovered during internal testing and affects all versions of the Java driver that support CSFLE. The Java async, Scala, and reactive streams drivers are not impacted. This vulnerability does not impact driver traffic payloads with CSFLE-supported key services originating from applications residing inside the AWS, GCP, and Azure network fabrics due to compensating controls in these environments. This issue does not impact driver workloads that don’t use Field Level Encryption.

Affected Packages

14 total 14 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.mongodb:mongodb-driver`	≥ 3.11.0&&< 3.11.3	3.11.3`org.mongodb:mongodb-driver:3.11.3`
☕Maven	`org.mongodb:mongodb-driver`	≥ 3.12.0&&< 3.12.8	3.12.8`org.mongodb:mongodb-driver:3.12.8`
☕Maven	`org.mongodb:mongodb-driver-sync`	≥ 4.0.0&&< 4.0.6	4.0.6`org.mongodb:mongodb-driver-sync:4.0.6`
☕Maven	`org.mongodb:mongodb-driver-sync`	≥ 4.1.0&&< 4.1.2	4.1.2`org.mongodb:mongodb-driver-sync:4.1.2`
☕Maven	`org.mongodb:mongodb-driver-sync`	≥ 4.2.0&&< 4.2.1	4.2.1`org.mongodb:mongodb-driver-sync:4.2.1`
☕Maven	`org.mongodb:mongo-java-driver`	≥ 3.11.0&&< 3.11.3	3.11.3`org.mongodb:mongo-java-driver:3.11.3`

Affected Products

2 products · 7 configurations

Application

java drivermongodb

≥ 4.2.0 && < 4.2.1

range

Application

quarkusquarkus

< 1.13.3

1 version

1.13.3

Detection & mitigation playbook

Open-source dependency

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

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

Product	Fixed in	Advisory
Red Hat Integration	`mongodb-driver`	RHSA-2021:4918
Red Hat Integration Camel Quarkus 2	see advisory	RHSA-2021:4767
Red Hat Integration Debezium 1.4.2	`mongodb-driver`	RHSA-2021:0871

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-rghw-6px2-fgwc in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.8/10CVSS v3 base

Vector breakdown

Attack Vector

Adjacent

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Raw vector

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

CWE Classification

CWE-295CWE-295

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

May 24, 2022

Last updated

Feb 16, 2024

Identifiers

GHSA-rghw-6px2-fgwc

References

Advisorynvd.nist.gov · CVE 2021 20328 Webjira.mongodb.org · JAVA 4017

Related vulnerabilities

This CVE is medium severity; 7 of 8 other CVEs with CWE-295 are rated as high or higher (top: critical).

CVE-2026-119189CVE-2026-118780CVE-2026-119190GHSA-5xjx-3w67-w9x9CVE-2026-109383GHSA-6q48-6c7w-9gw2GHSA-hq85-5cpj-mr62CVE-2026-70194Browse all CWE-295

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024

Improper Certificate Validation in MongoDBGHSA-rghw-6px2-fgwc

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is GHSA-rghw-6px2-fgwc in your dependencies?