CVE-2022-0265: XML External Entity Reference in Hazelcast

com.hazelcast:hazelcast Updated 02 Oct 2025

Summary

04/03/2022
Yes i
Critical
9.8

CVE-2022-0265: XML External Entity Reference in Hazelcast. Affects com.hazelcast:hazelcast versions >= 5.1-beta1, < 5.1. Fixed in 5.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Hazelcast is an open-source in-memory data grid solution that provides distributed caching, distributed computing, and distributed messaging capabilities. It is commonly used in Java applications to improve performance and scalability. However, a vulnerability has been discovered in Hazelcast that allows for XML External Entity (XXE) attacks.

Vulnerability Detail

The vulnerability arises from the use of the AbstractXmlConfigRootTagRecognizer() function in Hazelcast. This function utilizes a SAXParser generated from a SAXParserFactory without the FEATURE_SECURE_PROCESSING set. As a result, it becomes susceptible to XXE attacks, where an attacker can exploit the parsing of XML input to read arbitrary files or execute remote code. This vulnerability has a CVSS score of 9.8, indicating its critical severity.

How To Fix

Latest published version: 5.7.0 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

5.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading to the latest version of Hazelcast is not immediately feasible, a temporary workaround is to disable the parsing of XML configuration files. This can be achieved by modifying the application's configuration to use alternative configuration formats, such as properties or YAML files.

Conclusion

The vulnerability CVE-2022-0265 in Hazelcast exposes applications to XML External Entity (XXE) attacks, which can result in unauthorized access, remote code execution, or denial of service. It is crucial to upgrade to Hazelcast version 5.1 or later and apply the recommended fix to mitigate this vulnerability. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for com.hazelcast:hazelcast →

Share this vulnerability

FAQ

Hazelcast is an open-source in-memory data grid solution that provides distributed caching, distributed computing, and distributed messaging capabilities. It is commonly used in Java applications to improve performance and scalability.

An XML External Entity (XXE) attack is a type of security vulnerability that exploits the parsing of XML input. By injecting malicious XML entities, an attacker can read arbitrary files or execute remote code.

This vulnerability allows an attacker to perform XXE attacks, potentially leading to unauthorized access to sensitive information, remote code execution, or denial of service.

To fix this vulnerability, upgrade to Hazelcast version 5.1 or later and ensure the FEATURE_SECURE_PROCESSING flag is set on the SAXParserFactory. Keeping software dependencies up to date is also important.

A temporary workaround is to disable the parsing of XML configuration files and use alternative formats such as properties or YAML files.

Related vulnerabilities

Recent vulnerabilities recorded for com.hazelcast:hazelcast.

How To Fix

Latest published version: 5.7.0 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

5.1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback