python-jwt security update
setup.py test %endif Security Fix(es): PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT PyJWKClient is affected because redirect destinations are not revalidated against the JWKS trust boundary. This occurs when a configured trusted JWKS endpoint returns an attacker-influenced redirect. As a result, PyJWKClient follows the redirect and consumes the redirected response as key material. Consequently, forwarded credentials may be disclosed or verification keys may be substituted. This issue is fixed in version 2.14.0.(CVE-2026-102267) PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, is_pem_format in jwt/utils.py is affected because is_pem_format does not recognize every PEM representation accepted by the cryptography loader. This occurs when an application mixes HMAC and asymmetric algorithms and supplies a mutated public-key PEM as raw key bytes. As a result, HMACAlgorithm.prepare_key treats the unrecognized asymmetric public key as an HMAC secret. Consequently, an attacker who knows the public key can forge authenticated HMAC tokens. This issue is fixed in version 2.14.0.(CVE-2026-102268) PyJWT is a Python implementation of JSON Web Token standards. From 2.4.0 until 2.14.0, PyJWT HMACAlgorithm.prepare_key is affected because asymmetric-key guard relies on textual markers that are absent from DER encoding. This occurs when an application mixes HMAC and asymmetric algorithms and supplies a DER public key as the sh
- Products
- python-jwt
- Affected versions
- Not specified
- Fixed versions
- 2.8.0-6.oe2403sp4
- CVEs
- CVE-2026-102267, CVE-2026-102268, CVE-2026-102271
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 20:40 UTC · Revision 1
Source evidence
setup.py test %endif Security Fix(es): PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT PyJWKClient is affected because redirect destinations are not revalidated against the JWKS trust boundary. This occurs when a configured trusted JWKS endpoint returns an attacker-influenced redirect. As a result, PyJWKClient follows the redirect and consumes the redirected response as key material. Consequently, forwarded credentials may be disclosed or verification keys may be substituted. This issue is fixed in version 2.14.0.(CVE-2026-102267) PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, is_pem_format in jwt/utils.py is affected because is_pem_format does not recognize every PEM representation accepted by the cryptography loader. This occurs when an application mixes HMAC and asymmetric algorithms and supplies a mutated public-key PEM as raw key bytes. As a result, HMACAlgorithm.prepare_key treats the unrecognized asymmetric public key as an HMAC secret. Consequently, an attacker who knows the public key can forge authenticated HMAC tokens. This issue is fixed in version 2.14.0.(CVE-2026-102268) PyJWT is a Python implementation of JSON Web Token standards. From 2.4.0 until 2.14.0, PyJWT HMACAlgorithm.prepare_key is affected because asymmetric-key guard relies on textual markers that are absent from DER encoding. This occurs when an application mixes HMAC and asymmetric algorithms and supplies a DER public key as the sh
osv:OESA-2026-4385
python-jwt
Fixed versions: 2.8.0-6.oe2403sp4
Complete source record
{
"id": "fba9af21ed54014fb6ccaa18cb8fa4f8125218e39c9bc0eae27573d1e8e16433",
"url": "https://osv.dev/vulnerability/OESA-2026-4385",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "python-jwt security update",
"summary": "setup.py test %endif Security Fix(es): PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT PyJWKClient is affected because redirect destinations are not revalidated against the JWKS trust boundary. This occurs when a configured trusted JWKS endpoint returns an attacker-influenced redirect. As a result, PyJWKClient follows the redirect and consumes the redirected response as key material. Consequently, forwarded credentials may be disclosed or verification keys may be substituted. This issue is fixed in version 2.14.0.(CVE-2026-102267) PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, is_pem_format in jwt/utils.py is affected because is_pem_format does not recognize every PEM representation accepted by the cryptography loader. This occurs when an application mixes HMAC and asymmetric algorithms and supplies a mutated public-key PEM as raw key bytes. As a result, HMACAlgorithm.prepare_key treats the unrecognized asymmetric public key as an HMAC secret. Consequently, an attacker who knows the public key can forge authenticated HMAC tokens. This issue is fixed in version 2.14.0.(CVE-2026-102268) PyJWT is a Python implementation of JSON Web Token standards. From 2.4.0 until 2.14.0, PyJWT HMACAlgorithm.prepare_key is affected because asymmetric-key guard relies on textual markers that are absent from DER encoding. This occurs when an application mixes HMAC and asymmetric algorithms and supplies a DER public key as the sh",
"evidence": "osv:OESA-2026-4385",
"products": [
{
"name": {
"value": "python-jwt",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "2.8.0-6.oe2403sp4",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "critical",
"structured": {
"id": "OESA-2026-4385",
"aliases": [
"OESA-2026-4385"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "2.8.0-6.oe2403sp4"
}
]
}
],
"package": {
"name": "python-jwt",
"purl": "pkg:rpm/openEuler/python-jwt&distro=openEuler-24.03-LTS-SP4",
"ecosystem": "openEuler:24.03-LTS-SP4"
},
"database_specific": {
"source": "https://repo.openeuler.org/security/data/osv/OESA-2026-4385.json"
},
"ecosystem_specific": {
"src": [
"python-jwt-2.8.0-6.oe2403sp4.src.rpm"
],
"noarch": [
"python-jwt-help-2.8.0-6.oe2403sp4.noarch.rpm",
"python3-jwt-2.8.0-6.oe2403sp4.noarch.rpm"
]
}
}
],
"modified": "2026-10-16T12:15:11.183383808Z",
"provider": "osv",
"upstream": [
"CVE-2026-102267",
"CVE-2026-102268",
"CVE-2026-102271"
],
"references": [
"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4385",
"https://nvd.nist.gov/vuln/detail/CVE-2026-102267",
"https://nvd.nist.gov/vuln/detail/CVE-2026-102268",
"https://nvd.nist.gov/vuln/detail/CVE-2026-102271"
],
"provider_metadata": {
"severity": "Critical"
}
},
"related_cves": [
{
"value": "CVE-2026-102267",
"evidence": "/upstream"
},
{
"value": "CVE-2026-102268",
"evidence": "/upstream"
},
{
"value": "CVE-2026-102271",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 340820,
"published_at": "2026-10-16T12:00:01+00:00"
}