Answer in brief
CVE-2022-39366 records a Critical severity (CVSS 9.9) vulnerability in acryl-datahub missing JWT signature check. The current sources do not mark it as known exploited. The current feed maps acryl-datahub (pip), acryl-datahub (pypi). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps acryl-datahub (pip), acryl-datahub (pypi). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| acryl-datahubpip | <0.8.45 | 0.8.45 |
| acryl-datahubpypi | >=0 <0.8.45 | 0.8.45 |
Published upstream
Oct 31, 2022
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Oct 26, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Oct 26, 2026
# Missing JWT signature check (`GHSL-2022-078`) The [`StatelessTokenService`](https://github.com/datahub-project/datahub/blob/aa146db611e3a4ca3aa17bb740783f789d4444d3/metadata-service/auth-impl/src/main/java/com/datahub/authentication/token/StatelessTokenService.java#L30) 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`](https://github.com/datahub-project/datahub/blob/aa146db611e3a4ca3aa17bb740783f789d4444d3/metadata-service/auth-impl/src/main/java/com/datahub/authentication/token/StatelessTokenService.java#L134) 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 authentication bypass. #### Resources * [CodeQL: Missing JWT signature check](https://codeql.github.com/codeql-query-help/java/java-missing-jwt-signature-check/)
Quoted source text, attributed separately from HOL analysis.