Unsafe Deserialization in DataHub (CVE-2026-44501)
Summary
Vulnerability in DataHub (CVE-2026-44501). Risk of unauthorized operations or information disclosure. Exploitable via GET /callback/oidc. Mitigation: upgrade to 1.5.0.3 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44501 has been found in DataHub.
Attackers can target a specific entry point like GET /callback/oidc over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade DataHub to 1.5.0.3 or later.
If unsure, ask your IT team or search "DataHub CVE-2026-44501" on the vendor's site.
CVE-2026-44501 (DataHub) — CWE-502 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /callback/oidc
Patched: 1.5.0.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in DataHub. Attackers reach the vulnerable code path via GET /callback/oidc.
Check the vendor advisory for the affected versions of DataHub. Attack surface: GET /callback/oidc.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 1.5.0.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /callback/oidc requests with malformed payloads or SQL meta-characters. Run grep -r 'DataHub' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'DataHub' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
DataHubを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /callback/oidc' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /callback/oidcへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade DataHub to 1.5.0.3ステージング環境で 1.5.0.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /callback/oidc on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。