acryl-datahub missing JWT signature check

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.9 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:L

EPSS

• CVE-2022-39366: 1.11% estimated exploitation activity in the next 30 days; percentile 66.04 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Missing JWT signature check (`GHSL-2022-078`) 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.

Impact This issue may lead to an…

Published by the source

31 Oct 2022, 22:42 UTC

Last modified by the source

26 Oct 2026, 21:15 UTC

Source last checked

27 Oct 2026, 06:15 UTC

1. Revision 4 · amended · 27 Oct 2026

   Amended from osv record GHSA-r8gm-v65f-c973

2. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-r8gm-v65f-c973

3. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-r8gm-v65f-c973

4. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-r8gm-v65f-c973

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-39366

Advisory: acryl-datahub missing JWT signature check
IDs: CVE-2022-39366, GHSA-r8gm-v65f-c973
Record: https://patchnext.com/advisories/cve-2022-39366 (revision 4, source checked 27 Oct 2026, 06:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: acryl-datahub 0.8.45. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI acryl-datahub: affected < 0.8.45; fixed in 0.8.45

## Suggested inspection (read-only)
- `python -m pip show acryl-datahub`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on acryl-datahub.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-r8gm-v65f-c973 (OSV record GHSA-r8gm-v65f-c973 lists affected ranges: PyPI acryl-datahub >=0 <0.8.45 (fixed))
- Verified: https://github.com/advisories/GHSA-r8gm-v65f-c973 (GitHub-reviewed advisory GHSA-r8gm-v65f-c973 lists affected ranges: PyPI acryl-datahub >=0 <0.8.45)

Commands are suggestions: review each one before running it.