How severe is CVE-2022-39366?

CVE-2022-39366 has a CVSS 3.x base score of 9.9, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity high, and availability low.

Is CVE-2022-39366 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (54th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-39366?

CVE-2022-39366 affects Datahub. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2022-39366?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2022-39366 published?

CVE-2022-39366 was published on 2022-10-28 and last updated on 2026-06-17.

CVE-2022-39366

CVE-2022-39366 is a critical-severity vulnerability in Datahub with a CVSS 3.x base score of 9.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-347.

Key facts

Severity: Critical (CVSS 3.x base score 9.9)
EPSS exploit prediction: 1% (54th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-347
Affected product: Datahub
Published: 2022-10-28
Last modified: 2026-06-17

Description

DataHub is an open-source metadata platform. Prior to version 0.8.45, the `StatelessTokenService` of the DataHub metadata service (GMS) does not verify the signature of JWT tokens. This allows an attacker to connect to DataHub instances as any user if Metadata Service authentication is enabled. This vulnerability occurs because the `StatelessTokenService` of the Metadata service uses the `parse` method of `io.jsonwebtoken.JwtParser`, which does not perform a verification of the cryptographic token signature. This means that JWTs are accepted regardless of the used algorithm. This issue may lead to an authentication bypass. Version 0.8.45 contains a patch for the issue. There are no known workarounds.

Frequently asked questions

What is CVE-2022-39366?: DataHub is an open-source metadata platform. Prior to version 0.8.45, the `StatelessTokenService` of the DataHub metadata service (GMS) does not verify the signature of JWT tokens. This allows an attacker to connect to DataHub instances as any user if Metadata Service authentication is enabled. This vulnerability occurs because the `StatelessTokenService` of the Metadata service uses the `parse` method of `io.jsonwebtoken.JwtParser`, which does not perform a verification of the cryptographic token signature. This means that JWTs are accepted regardless of the used algorithm. This issue may lead to an authentication bypass. Version 0.8.45 contains a patch for the issue. There are no known workarounds.
How severe is CVE-2022-39366?: CVE-2022-39366 has a CVSS 3.x base score of 9.9, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity high, and availability low.
Is CVE-2022-39366 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (54th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-39366?: CVE-2022-39366 affects Datahub. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-39366?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2022-39366 published?: CVE-2022-39366 was published on 2022-10-28 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:datahub:datahub:*:*:*:*:*:*:*:*

More vulnerabilities in Datahub

CVE-2023-25560 — High (CVSS 8.2): DataHub is an open-source metadata platform. The AuthServiceClient which is responsible for creation of new accounts,…
CVE-2023-25559 — High (CVSS 8.2): DataHub is an open-source metadata platform. When not using authentication for the metadata service, which is the…
CVE-2026-25644 — High (CVSS 7.5): DataHub is an open-source metadata platform. Prior to version 1.3.1.8, the LDAP ingestion source is vulnerable to MITM…
CVE-2023-25557 — High (CVSS 7.5): DataHub is an open-source metadata platform. The DataHub frontend acts as a proxy able to forward any REST or GraphQL…
CVE-2023-25562 — Medium (CVSS 6.9): DataHub is an open-source metadata platform. In versions of DataHub prior to 0.8.45 Session cookies are only cleared on…
CVE-2023-25561 — Medium (CVSS 5.7): DataHub is an open-source metadata platform. In the event a system is using Java Authentication and Authorization…

All CVEs affecting Datahub →

Other CWE-347 (Improper Verification of Cryptographic Signature) vulnerabilities

CVE-2026-48558 — Critical (CVSS 10.0): SimpleHelp versions 5.5.15 and prior and 6.0 pre-release versions contain an authentication bypass vulnerability in the…
CVE-2023-25574 — Critical (CVSS 10.0): `jupyterhub-ltiauthenticator` is a JupyterHub authenticator for learning tools interoperability (LTI).…
CVE-2024-45409 — Critical (CVSS 10.0): The Ruby SAML library is for implementing the client side of a SAML authorization. Ruby-SAML in <= 12.2 and 1.13.0 <=…
CVE-2024-32962 — Critical (CVSS 10.0): xml-crypto is an xml digital signature and encryption library for Node.js. In affected versions the default…
CVE-2022-24884 — Critical (CVSS 10.0): ecdsautils is a tiny collection of programs used for ECDSA (keygen, sign, verify). `ecdsa_verify_[prepare_]legacy()`…
CVE-2021-33885 — Critical (CVSS 10.0): An Insufficient Verification of Data Authenticity vulnerability in B. Braun SpaceCom2 prior to 012U000062 allows a…

Browse all CWE-347 (Improper Verification of Cryptographic Signature) vulnerabilities →