limbo.watch

In limbo for 154 days

GHSA-pwmg-mvjw-4m23

dhis2-core on Maven · published in dhis2/dhis2-core

Read the advisory on GitHub ↗

Facts

Severity
High · CVSS score 8.8CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Package name
dhis2-coreAs entered. Doesn’t look like a valid Maven package name, so scanners can’t match it. How to fix it
Affected versions
2.37, 2.38, 2.39, 2.40.x before 2.40.11.1/2.40.12, 2.41.x before 2.41.8.2, 2.42.x before 2.42.5.1, 2.43.0 before 2.43.0.1, 2.44 development branch before PR #24162As entered by the maintainer. Not reviewed. Scanners can’t read this range. How to fix it
Fixed in
2.37-EOS (2026-06-09), 2.38-EOS (2026-06-09), 2.39-EOS (2026-06-09), 2.40.11.1, 2.40.12, 2.41.8.2, 2.42.5.1, 2.43.0.1, 2.44 development branch after PR #24162
CVE
CVE-2026-55084 · published
GitHub Advisory Database
Not reviewed
OSV.dev
Not present
Other CVEs pointing here
None found in the CVE List

If you use dhis2-core 2.37, 2.38, 2.39, 2.40.x before 2.40.11.1/2.40.12, 2.41.x before 2.41.8.2, 2.42.x before 2.42.5.1, 2.43.0 before 2.43.0.1, 2.44 development branch before PR #24162

The fixed-version field says “2.37-EOS (2026-06-09), 2.38-EOS (2026-06-09), 2.39-EOS (2026-06-09), 2.40.11.1, 2.40.12, 2.41.8.2, 2.42.5.1, 2.43.0.1, 2.44 development branch after PR #24162”. Check the advisory for which version fixes it. Dependabot, npm audit and OSV-Scanner won’t flag this yet.

Timeline

  1. 2026-06-11 14:48 UTC

    Published by the maintainers

    Cites CVE-2026-55084

  2. 2026-10-31 12:45 UTC

    First seen by Limbowatch

    not reviewed · not in OSV

  3. Waiting

    Reviewed by GitHub

  4. Waiting

    In OSV; scanners can see it

Machine-readable record: feed/GHSA-pwmg-mvjw-4m23.json