CVE-2026-55083: dhis2-core · Deserialization of Untrusted Data
Affects dhis2-coreSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 2.43.0.1 or 2.42.5.1 as a priority.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.43.0.1, 2.42.5.1
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade dhis2-core and dhis2/dhis2-core to 2.43.0.1 or 2.42.5.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| dhis2dhis2-core | Affected
| Fixed in
|
| dhis2dhis2-core | Affected
| Fixed in
|
GitHubdhis2/dhis2-corepkg:github/dhis2/dhis2-coreOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade affected DHIS2 instances to version 2.42.5.1, 2.43.0.1, or later (including 2.44) where the vulnerability has been patched. No other mitigations are specified. Patch status is confirmed fixed in these versions.
Description
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.