{"answers":{"affected":"3 open source packages ship an affected version, including acryl-datahub. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39366 exists.","fix":"Upgrade acryl-datahub to 0.8.45 or later.","what":"CVE-2022-39366 is a critical authentication bypass vulnerability in datahub-project datahub, published on 28 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-39366 and fix it if it is affected.\n\nWhat it is: CVE-2022-39366 is a critical authentication bypass vulnerability in datahub-project datahub, published on 28 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39366 exists.\n\nAffected packages and fixed versions:\n- acryl-datahub (PyPI): affected all versions; fixed in 0.8.45\n- acryl-datahub (PyPI): affected all versions; fixed in 0.8.45\n- acryl-datahub (PyPI): affected all versions; fixed in 0.8.45\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-2022-39366/ (Markdown: https://insights.sbomify.com/CVE-2022-39366/index.md)","id":"CVE-2022-39366","markdown":"https://insights.sbomify.com/CVE-2022-39366/index.md","name":"CVE-2022-39366","record":{"aliases":["GHSA-r8gm-v65f-c973","PYSEC-2026-252"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"DataHub metadata platform","requires_auth":"none","summary":"Attackers can bypass authentication and impersonate any user in DataHub if Metadata Service authentication is enabled, due to missing JWT signature verification.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"datahub","vendor":"datahub"}],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-303","name":"Incorrect Implementation of Authentication Algorithm"},{"id":"CWE-287","name":"Improper Authentication"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"DataHub missing JWT signature check","id":"CVE-2022-39366","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":3,"n_references":5,"next":{"headline":"Vulnerability in handling of uploaded QTI ZIP files","id":"CVE-2022-39367"},"packages":[{"ecosystem":"PyPI","fixed":["0.8.45"],"introduced":["0"],"last_affected":[],"package":"acryl-datahub","purl":null,"source":"GHSA-r8gm-v65f-c973"},{"ecosystem":"PyPI","fixed":["0.8.45"],"introduced":["0"],"last_affected":[],"package":"acryl-datahub","purl":"pkg:pypi/acryl-datahub","source":"GHSA-r8gm-v65f-c973"},{"ecosystem":"PyPI","fixed":["0.8.45"],"introduced":["0"],"last_affected":[],"package":"acryl-datahub","purl":"pkg:pypi/acryl-datahub","source":"PYSEC-2026-252"}],"prev":{"headline":"RCE vulnerability in Pimcore/Mail \u0026 Dynamic Text Layout","id":"CVE-2022-39365"},"products":["datahub"],"published":"2022-10-28","related":[{"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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["datahub-project"]},"summary":"Attackers can bypass authentication and impersonate any user in DataHub if Metadata Service authentication is enabled, due to missing JWT signature verification.","url":"https://insights.sbomify.com/CVE-2022-39366/"}