Critical-Severity Insecure Deserialization Flaw in dhis2-core Tracked as CVE-2026-55083
A newly published critical vulnerability in dhis2-core carries a CVSS score of 9.1. Here is what is affected and how to respond.
Key points
- CVE-2026-55083 affects dhis2-core.
- CVSS 9.1 (Critical).
- No exploitation confirmed yet.
dhis2-core is affected by CVE-2026-55083, a insecure deserialization that the National Vulnerability Database rates 9.1 out of 10.
At a glance
- CVE
- CVE-2026-55083
- Product
- dhis2-core
- CVSS
- 9.1 Critical
- Weakness
- insecure deserialization
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: 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 versions
| Vendor | Product | Versions |
|---|---|---|
| Dhis2 | dhis2-core | >= 2.42.0, < 2.42.5.1, >= 2.43.0, < 2.43.0.1 |
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H.
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
Background: Insecure deserialization
Look for base64-encoded parameters, unexpected object instantiation, or state changes that bypass authentication. Inspect input handling for unvalidated deserialization. Use allowlists for expected data types and verify integrity with digital signatures to prevent arbitrary code execution.
Read the full guide: Warning Signs of Insecure Deserialization in Web Applications
What to do and how to stay safe: CVE-2026-55083
- Patch scores alone ignore context like network exposure and asset criticality.
- You must map vulnerabilities to specific business risks to prioritize correctly.
- Continuous exposure data replaces static scanning for accurate prioritization.
Prioritize vulnerabilities by actual exploitability and business impact, not by theoretical severity scores. Update your asset context and exposure data continuously to maintain accurate risk rankings.
Step-by-step guide: Risk Based Vulnerability Management: Prioritize Fixes by Actual Threat
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-55083?
CVE-2026-55083 is a insecure deserialization vulnerability in dhis2-core.
How severe is CVE-2026-55083?
It has a CVSS score of 9.1 Critical.
Is CVE-2026-55083 being exploited?
There is no public confirmation of exploitation at the time of publication.
