CVE-2026-44501 DataHub OIDC REDIRECT_URL Cookie Deserialization Vulnerability

What is CVE-2026-44501?

CVE-2026-44501 is a medium-severity unsafe deserialization vulnerability in datahub-project datahub, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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 configured OIDC identity provider This vulnerability is fixed in 1.5.0.3.

Weakness: CWE-502

Which versions are affected by CVE-2026-44501?

It affects 1 product.

Products include Datahub Datahub.

How do I fix CVE-2026-44501?

No fix has been published for CVE-2026-44501 yet. Limit exposure of the affected software until one is available.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2026-44501 being exploited?

There is no known exploitation of CVE-2026-44501 in the wild and no public exploit code.

Other vulnerabilities in datahub-project datahub

• CVE-2022-39366 DataHub missing JWT signature check Critical 9.9
• CVE-2023-25559 System account impersonation in DataHub High 8.2
• CVE-2023-25560 JSON Injection in DataHub High 8.2
• CVE-2026-25644 DataHub's LDAP Ingestion Source vulnerable to MITM attack through TLS downgrade High 7.5
• CVE-2023-25557 Server-Side Request Forgery in DataHub High 7.5

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as GHSA-rjf9-p49v-42c4.