CVE-2026-44501: DataHub is an open-source metadata platform

Q: How do I fix CVE-2026-44501?

datahub: upgrade to 1.5.0.3. Exact commands for each OS are on this page.

Q: Is CVE-2026-44501 being exploited?

CVE-2026-44501 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-44501 affect?

CVE-2026-44501 affects datahub. Severity is medium (CVSS 4.3). DataHub is an open-source metadata platform. Prior to 1.5.0.3, The DataHub frontend (datahub-frontend-react) deserializes attacker-controlled Java objects from the REDIRECT_URL HTTP cookie during the OIDC callback flow, with no integrity pr

Q: How urgent is CVE-2026-44501?

Priority 16/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2026-44501 is a medium-severity flaw (CVSS 4.3) affecting datahub. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

DataHub is an open-source metadata platform. Prior to 1.5.0.3, The DataHub frontend (datahub-frontend-react) deserializes attacker-controlled Java objects from the REDIRECT_URL HTTP cookie during the OIDC callback flow, with no integrity protection (no HMAC, no encryption). This is a Deserialization of Untrusted Data vulnerability (CWE-502) affecting the GET /callback/oidc endpoint. Successful exploitation requires a valid user account in the con

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.1% (top 97%)
CISA exploited list	No
Weakness	CWE-502
Published	2026-05-14
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: datahub

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-14 16:16 UTCPublished CVE record published
2026-06-17 10:50 UTCUpdated Record last modified

datahub datahub UPGRADE

Affected: < 1.5.0.3

Fixed in: 1.5.0.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy datahub || rpm -q datahub || datahub --version

2. UPGRADE to 1.5.0.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade datahub

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade datahub

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-44501?

datahub: upgrade to 1.5.0.3. Exact commands for each OS are on this page.

Is CVE-2026-44501 being exploited?

CVE-2026-44501 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-44501 affect?

CVE-2026-44501 affects datahub. Severity is medium (CVSS 4.3). DataHub is an open-source metadata platform. Prior to 1.5.0.3, The DataHub frontend (datahub-frontend-react) deserializes attacker-controlled Java objects from the REDIRECT_URL HTTP cookie during the OIDC callback flow, with no integrity pr

How urgent is CVE-2026-44501?

Priority 16/100. No elevated risk signals yet.

Software pages

Java vulnerabilities · React vulnerabilities

References

← Back to latest CVEs