# CVE-2026-44501: DataHub OIDC REDIRECT_URL Cookie Deserialization Vulnerability

> Attacker with valid OIDC account can execute arbitrary code via deserialization of untrusted Java objects in the REDIRECT_URL cookie.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-rjf9-p49v-42c4

## 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 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-44501?

It affects 1 product.


Products: 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.

## 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](https://insights.sbomify.com/CVE-2022-39366/): DataHub missing JWT signature check (critical 9.9)
- [CVE-2023-25559](https://insights.sbomify.com/CVE-2023-25559/): System account impersonation in DataHub (high 8.2)
- [CVE-2023-25560](https://insights.sbomify.com/CVE-2023-25560/): JSON Injection in DataHub (high 8.2)
- [CVE-2026-25644](https://insights.sbomify.com/CVE-2026-25644/): DataHub's LDAP Ingestion Source vulnerable to MITM attack through TLS downgrade (high 7.5)
- [CVE-2023-25557](https://insights.sbomify.com/CVE-2023-25557/): Server-Side Request Forgery in DataHub (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44501 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-44501 in the wild and no public exploit code.

Affected product: datahub-project datahub. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44501/ (Markdown: https://insights.sbomify.com/CVE-2026-44501/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44501
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44501
- OSV: https://osv.dev/vulnerability/CVE-2026-44501

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44501/
Summaries are generated and may contain mistakes; the official description above is the record.