NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

XML External Entity Reference in HazelcastGHSA-99wh-973f-779p

CRITICALFix: hazelcast/hazelcast#20407

GHSA-99wh-973f-779p is a critical-severity (CVSS 9.8) XML External Entity (XXE) vulnerability in com.hazelcast:hazelcast. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for com.hazelcast:hazelcast — see the affected versions and patch details below.

Also known asCVE-2022-0265
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
3 known
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk
1.14%4.08%7.02%9.96%8.3%2.8%May 26Sep 26Nov 26

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

1 pkg affected
☕com.hazelcast:hazelcast

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

The AbstractXmlConfigRootTagRecognizer() function makes use of SAXParser generated from a SAXParserFactory with no FEATURE_SECURE_PROCESSING set, allowing for XXE attacks.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.hazelcast:hazelcast≥ 5.1-beta1&&< 5.15.1com.hazelcast:hazelcast:5.1

Affected Products

1 product · 1 configurations
Application
hazelcasthazelcast
1 version
5.1
Exploits & PoCs
3

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

Improper Restriction of XML External Entity Reference in GitHub reposito…

huntr.devNVDMar 2022

Report on github.com

github.comGithubApr 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update com.hazelcast:hazelcast to 5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-99wh-973f-779p is resolved across your whole dependency graph.

  3. 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

The AbstractXmlConfigRootTagRecognizer() function makes use of SAXParser generated from a SAXParserFactory with no FEATURE_SECURE_PROCESSING set, allowing for XXE attacks.
O3 Security · Impact-Aware SCA

Is GHSA-99wh-973f-779p in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
XML External Entity Reference in Hazelcast (Critical 9.8)