Unsafe Java deserialization enables remote code execution in DHIS2 Core

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-55083?

CVE-2026-55083 is a vulnerability classified as Deserialization of Untrusted Data, affecting dhis2-core (affected versions: >= 2.42.0, < 2.42.5.1 and >= 2.43.0, < 2.43.0.1). This vulnerability is rated Critical, with a CVSS score of 9.1. Current sources do not report this vulnerability as exploited.

Overview

Original source data

DHIS2 is a flexible information system for data capture, management, validation, analytics and visualization. From versions 2.42.0 to before 2.42.5.1, and from versions 2.43.0 to before 2.43.0.1, DHIS2 is vulnerable to remote code execution (RCE) via unsafe Java deserialization. This issue has been patched in versions 2.42.5.1, 2.43.0.1, and 2.44.

Affected products and scope

  • dhis2-core from 2.42.0 through before 2.42.5.1 is affected; 2.42.5.1 is the confirmed fix for this branch.
  • dhis2-core from 2.43.0 through before 2.43.0.1 is affected; 2.43.0.1 is the confirmed fix for this branch.
  • The CNA advisory identifies the 2.44 development branch before PR #24162 as affected and revisions after PR #24162 as patched. The normalized description also lists 2.44 as patched, but does not establish an open-ended range covering every later revision or parallel release branch.

Technical details

DHIS2 Core processes untrusted Java serialized data without sufficiently validating the safety of the resulting object, which is classified as CWE-502. Attacker-controlled serialized data may trigger remote code execution in the DHIS2 process when the required access conditions are met. The supplied evidence establishes network reachability, high required privileges, and no user interaction; the impact scope may extend beyond the initially vulnerable component. The available evidence does not identify the endpoint, serialized object format, specific sink, or gadget chain, so those implementation details should not be inferred.

Exploitability

The vulnerability is reachable over the network. The supplied scoring data describes low attack complexity, high required privileges, and no user interaction. The scope is marked as changed, indicating that successful exploitation may affect resources outside the original security boundary of the vulnerable component. The normalized record marks public_exploit as false and does not identify a known exploited status; this is not evidence that exploitation is impossible.

Technical impact

Successful exploitation could provide code execution in the DHIS2 server context and affect resources outside the original deserialization component's security boundary. Potential technical outcomes include data disclosure, data modification, or service disruption, with the extent depending on the service account's permissions and isolation controls. Because high privileges are required, the available record does not describe this as a directly unauthenticated attack path. The specific data at risk, gadget chain, and degree of lateral impact remain unknown.

Business impact

Code execution in the DHIS2 service context could allow an attacker to read or modify data available to that service account, depending on the deployment's permissions. The attacker could also disrupt the application or use the compromised server to affect other resources in the environment. The practical risk depends on the service account's permissions, network segmentation, and where high-privilege interfaces are exposed. The record provides no evidence of a specific breach, victim, or campaign.

Remediation

  1. Upgrade deployments on the 2.42 branch to exactly 2.42.5.1.
  2. Upgrade deployments on the 2.43 branch to exactly 2.43.0.1.
  3. For the 2.44 development branch, move to a revision after PR #24162 according to the CNA advisory's fix boundary. Do not treat a fix on this branch as proof that parallel branches are unaffected.
  4. If an upgrade cannot be completed immediately, isolate affected deployments and restrict network access to high-privilege interfaces to trusted sources. This is temporary risk reduction, not a vendor-confirmed workaround.
  5. After upgrading, verify the package or revision actually running and restart the required DHIS2 components so the patched code is loaded.

Detection

  1. Inventory all DHIS2 deployments and identify the version or revision of the Maven package dhis2-core.
  2. Compare each deployment with the affected and fixed boundaries in affected_summary, including the 2.44 development branch.
  3. Review network and application logs on DHIS2 servers for anomalous requests reaching functionality that processes serialized data. The specific endpoint is not established by the available evidence.
  4. Review server telemetry for unusual child-process or execution activity originating from the DHIS2 service. This is precautionary monitoring, not a confirmed IOC.
  5. Do not treat the absence of suspicious logs as proof of safety; prioritize version verification and upgrade validation.
Sources (20)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.