critical

CVE-2022-39227

python-jwt: token forgery with new claims

Published 23 Sep 2022Modified 17 Jun 2026CWE 290

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

NVD9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

GHSA9.3CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Red Hat9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Trivy's own label is CRITICAL. Rated critical by NVD, GHSA, CBL-Mariner. Rated lower by Red Hat (high).

Description

python-jwt is a module for generating and verifying JSON Web Tokens. Versions prior to 3.3.4 are subject to Authentication Bypass by Spoofing, resulting in identity spoofing, session hijacking or authentication bypass. An attacker who obtains a JWT can arbitrarily forge its contents without knowing the secret key. Depending on the application, this may for example enable the attacker to spoof other user's identities, hijack their sessions, or bypass authentication. Users should upgrade to version 3.3.4. There are no known workarounds.

Affected packages and fixed versions

Source	Package	Fixed in
CBL-Mariner 1.0	python-jwt	0:2.4.0-2.cm1
CBL-Mariner 2.0	python-jwt	0:2.4.0-2.cm2
pip::GitHub Security Advisory pip	python-jwt	3.3.4
Red Hat	python-jwt, python2-jwt	no fix listed

Show all 5 entries from 4 sources

Source	Package	Fixed in
CBL-Mariner 1.0	python-jwt	0:2.4.0-2.cm1
CBL-Mariner 2.0	python-jwt	0:2.4.0-2.cm2
pip::GitHub Security Advisory pip	python-jwt	3.3.4
Red Hat	python-jwt	no fix listed
Red Hat	python2-jwt	no fix listed

References

All 9 references

https://www.vicarius.io/vsociety/posts/authentication-bypass-in-python-jwt

What Attestkeep does with this

Inside your cluster, without you opening a spreadsheet.

KnowsThe scanner refreshes its vulnerability database every six hours.

FindsEvery admitted image is rescanned every 24 hours by default (scan.rescanInterval). When Trivy rates this vulnerability critical for the image's package source, it appears in the image's findings by name. Findings without a fix are left out unless includeUnfixed is on.

Tells youA critical_finding event goes to the channels subscribed to it: e-mail, Slack, Teams, a webhook, Jira, GitLab or GitHub.

RefusesWith a policy that blocks critical findings, a pod with this image is refused at admission, a rollback to it included. Pods already running are not evicted.

RecordsEach decision is recorded with the policy that ran and its hash, then sealed under a signed checkpoint.

Try Attestkeep

Read the docs