{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-44501 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-44501 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-44501 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-44501 in the wild and no public exploit code.\n\nAffected product: datahub-project datahub. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44501/ (Markdown: https://insights.sbomify.com/CVE-2026-44501/index.md)","id":"CVE-2026-44501","markdown":"https://insights.sbomify.com/CVE-2026-44501/index.md","name":"CVE-2026-44501","record":{"aliases":["GHSA-rjf9-p49v-42c4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"DataHub metadata platform","requires_auth":"low_privilege","summary":"Attacker with valid OIDC account can execute arbitrary code via deserialization of untrusted Java objects in the REDIRECT_URL cookie.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"datahub","vendor":"datahub"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"DataHub OIDC REDIRECT_URL Cookie Deserialization Vulnerability","id":"CVE-2026-44501","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Bugsink: SSRF bypass in `validate_webhook_url`","id":"CVE-2026-44502"},"packages":[],"prev":{"headline":"ZEBRA: Allocation Amplification in Inbound Network Deserializers","id":"CVE-2026-44500"},"products":["datahub"],"published":"2026-05-14","related":[{"cvss_score":9.9,"headline":"DataHub missing JWT signature check","id":"CVE-2022-39366","kev_date_added":null,"published":"2022-10-28"},{"cvss_score":8.2,"headline":"System account impersonation in DataHub","id":"CVE-2023-25559","kev_date_added":null,"published":"2023-02-10"},{"cvss_score":8.2,"headline":"JSON Injection in DataHub","id":"CVE-2023-25560","kev_date_added":null,"published":"2023-02-10"},{"cvss_score":7.5,"headline":"DataHub's LDAP Ingestion Source vulnerable to MITM attack through TLS downgrade","id":"CVE-2026-25644","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":7.5,"headline":"Server-Side Request Forgery in DataHub","id":"CVE-2023-25557","kev_date_added":null,"published":"2023-02-10"},{"cvss_score":6.9,"headline":"Failure to Invalidate Session on Logout in DataHub","id":"CVE-2023-25562","kev_date_added":null,"published":"2023-02-10"},{"cvss_score":5.7,"headline":"Login fail open on JAAS misconfiguration in DataHub","id":"CVE-2023-25561","kev_date_added":null,"published":"2023-02-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-14","vendors":["datahub-project"]},"summary":"Attacker with valid OIDC account can execute arbitrary code via deserialization of untrusted Java objects in the REDIRECT_URL cookie.","url":"https://insights.sbomify.com/CVE-2026-44501/"}