CVE-2023-25558: Deserialization of untrusted data in DataHub

Severity: high (CVSS 8.8 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 1.0% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2023-02-11 · updated 2026-06-17
Weakness: CWE-502

Description

DataHub is an open-source metadata platform. When the DataHub frontend is configured to authenticate via SSO, it will leverage the pac4j library. The processing of the `id_token` is done in an unsafe manner which is not properly accounted for by the DataHub frontend. Specifically, if any of the id_token claims value start with the {#sb64} prefix, pac4j considers the value to be a serialized Java object and will deserialize it. This issue may lead to Remote Code Execution (RCE) in the worst case. Although a `RestrictedObjectInputStream` is in place, that puts some restriction on what classes can be deserialized, it still allows a broad range of java packages and potentially exploitable with different gadget chains. Users are advised to upgrade. There are no known workarounds. This vulnerability was discovered and reported by the GitHub Security lab and is tracked as GHSL-2022-086.

Affected products

Datahub Project Datahub: before 0.9.5 — fixed in 0.9.5

How to fix

Upgrade to a fixed version: Datahub Project Datahub 0.9.5. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2023-25558 or the next vulnerability affects your stack