Search

Find a vulnerability

Search criteria ⓘ Use this form to refine search results.
Full-text search supports keyword queries with ranking and filtering.
You can combine vendor, product, and sources to narrow results.
Enable “Apply ordering” to sort by date instead of relevance.

    21 vulnerabilities found for python-jwt by azure linux

    AZL-105642 (CVE-2026-103001)

    Vulnerability from osv_azurelinux – Published: 2026-09-30 22:16 – Updated: 2026-11-01 07:13 – Source website
    VLAI
    Summary
    CVE-2026-103001 affecting package python-jwt for versions less than 2.15.1-1
    Details

    PyJWT is a Python implementation of JSON Web Token standards. From 2.11.0 through 2.13.0, PyJWT's PyJWT._merge_options() method can modify a caller-supplied mutable options mapping when verify_signature is false. If an application reuses that same mapping for a later decode() or decode_complete() call and changes verify_signature to true, the mapping can retain false values for expiration, not-before, issued-at, audience, issuer, subject, and JWT ID checks. A signed token with invalid registered claims can then be accepted without disabling signature verification, but applications that create a fresh options mapping for each call are not affected.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.15.1-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.15.1-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a Python implementation of JSON Web Token standards. From 2.11.0 through 2.13.0, PyJWT\u0027s PyJWT._merge_options() method can modify a caller-supplied mutable options mapping when verify_signature is false. If an application reuses that same mapping for a later decode() or decode_complete() call and changes verify_signature to true, the mapping can retain false values for expiration, not-before, issued-at, audience, issuer, subject, and JWT ID checks. A signed token with invalid registered claims can then be accepted without disabling signature verification, but applications that create a fresh options mapping for each call are not affected.",
      "id": "AZL-105642",
      "modified": "2026-11-01T07:13:08Z",
      "published": "2026-09-30T22:16:33Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-103001"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-103001 affecting package python-jwt for versions less than 2.15.1-1",
      "upstream": [
        "CVE-2026-103001"
      ]
    }

    AZL-105224 (CVE-2026-102272)

    Vulnerability from osv_azurelinux – Published: 2026-09-28 21:17 – Updated: 2026-11-01 07:13 – Source website
    VLAI
    Summary
    CVE-2026-102272 affecting package python-jwt for versions less than 2.15.1-1
    Details

    PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, HMACAlgorithm.prepare_key in jwt/algorithms.py is affected because raw-JWK detector does not normalize accepted Unicode byte-order marks before checking for JSON. This occurs when a public JWK is prefixed with a UTF-8 BOM and used in a mixed-algorithm verification path. As a result, public JWK bypasses asymmetric-key detection and becomes the HMAC secret. Consequently, an attacker who knows the public key can forge authenticated tokens. This issue is fixed in version 2.14.0.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.15.1-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.15.1-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, HMACAlgorithm.prepare_key in jwt/algorithms.py is affected because raw-JWK detector does not normalize accepted Unicode byte-order marks before checking for JSON. This occurs when a public JWK is prefixed with a UTF-8 BOM and used in a mixed-algorithm verification path. As a result, public JWK bypasses asymmetric-key detection and becomes the HMAC secret. Consequently, an attacker who knows the public key can forge authenticated tokens. This issue is fixed in version 2.14.0.",
      "id": "AZL-105224",
      "modified": "2026-11-01T07:13:08Z",
      "published": "2026-09-28T21:17:15Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-102272"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-102272 affecting package python-jwt for versions less than 2.15.1-1",
      "upstream": [
        "CVE-2026-102272"
      ]
    }

    AZL-105233 (CVE-2026-102275)

    Vulnerability from osv_azurelinux – Published: 2026-09-28 21:17 – Updated: 2026-11-01 07:13 – Source website
    VLAI
    Summary
    CVE-2026-102275 affecting package python-jwt for versions less than 2.15.1-1
    Details

    PyJWT is a Python implementation of JSON Web Token standards. From 2.1.0 until 2.15.0, PyJWT OKPAlgorithm.from_jwk in jwt/algorithms.py is affected because private-JWK import path does not compare the public key derived from d with x. This occurs when an OKP private JWK supplies non-corresponding x and d components. As a result, identity derived from x can differ from operations performed with d. Consequently, if an integration also accepts private key parameters from a proof header without rejecting them, an attacker may use a stolen sender-constrained token without the legitimate private key. This issue is fixed in version 2.15.0.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.15.1-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.15.1-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a Python implementation of JSON Web Token standards. From 2.1.0 until 2.15.0, PyJWT OKPAlgorithm.from_jwk in  jwt/algorithms.py is affected because private-JWK import path does not compare the public key derived from d with x. This occurs when an OKP private JWK supplies non-corresponding x and d components. As a result, identity derived from x can differ from operations performed with d. Consequently, if an integration also accepts private key parameters from a proof header without rejecting them, an attacker may use a stolen sender-constrained token without the legitimate private key. This issue is fixed in version 2.15.0.",
      "id": "AZL-105233",
      "modified": "2026-11-01T07:13:08Z",
      "published": "2026-09-28T21:17:15Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-102275"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-102275 affecting package python-jwt for versions less than 2.15.1-1",
      "upstream": [
        "CVE-2026-102275"
      ]
    }

    AZL-105227 (CVE-2026-102273)

    Vulnerability from osv_azurelinux – Published: 2026-09-28 21:17 – Updated: 2026-11-01 07:13 – Source website
    VLAI
    Summary
    CVE-2026-102273 affecting package python-jwt for versions less than 2.15.1-1
    Details

    PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, PyJWT HMACAlgorithm.prepare_key is affected because HMAC key guard only recognizes top-level public JWK forms and misses container representations. This occurs when an application allows HMAC and asymmetric algorithms and passes a public JWK container as the raw key. As a result, public asymmetric key material is accepted as the HMAC secret. Consequently, an attacker who knows the public key can forge a token with arbitrary authenticated claims. This issue is fixed in version 2.14.0.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.15.1-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.15.1-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, PyJWT HMACAlgorithm.prepare_key is affected because HMAC key guard only recognizes top-level public JWK forms and misses container representations. This occurs when an application allows HMAC and asymmetric algorithms and passes a public JWK container as the raw key. As a result, public asymmetric key material is accepted as the HMAC secret. Consequently, an attacker who knows the public key can forge a token with arbitrary authenticated claims. This issue is fixed in version 2.14.0.",
      "id": "AZL-105227",
      "modified": "2026-11-01T07:13:08Z",
      "published": "2026-09-28T21:17:15Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-102273"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-102273 affecting package python-jwt for versions less than 2.15.1-1",
      "upstream": [
        "CVE-2026-102273"
      ]
    }

    AZL-105236 (CVE-2026-102274)

    Vulnerability from osv_azurelinux – Published: 2026-09-28 21:17 – Updated: 2026-11-01 07:13 – Source website
    VLAI
    Summary
    CVE-2026-102274 affecting package python-jwt for versions less than 2.15.1-1
    Details

    PyJWT is a Python implementation of JSON Web Token standards. From 2.9.0 until 2.14.0, PyJWKSet does not catch the plain ValueError raised for malformed RSA JWK components by RSAAlgorithm.from_jwk in jwt/api_jwk.py. This occurs when a JWK Set contains a malformed RSA key alongside otherwise usable keys. As a result, one malformed member aborts construction of the entire PyJWKSet. Consequently, applications can experience authentication failures or request-level denial of service. This issue is fixed in version 2.14.0.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.15.1-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.15.1-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a Python implementation of JSON Web Token standards. From 2.9.0 until 2.14.0, PyJWKSet does not catch the plain ValueError raised for malformed RSA JWK components by RSAAlgorithm.from_jwk in  jwt/api_jwk.py. This occurs when a JWK Set contains a malformed RSA key alongside otherwise usable keys. As a result, one malformed member aborts construction of the entire PyJWKSet. Consequently, applications can experience authentication failures or request-level denial of service. This issue is fixed in version 2.14.0.",
      "id": "AZL-105236",
      "modified": "2026-11-01T07:13:08Z",
      "published": "2026-09-28T21:17:15Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-102274"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-102274 affecting package python-jwt for versions less than 2.15.1-1",
      "upstream": [
        "CVE-2026-102274"
      ]
    }

    AZL-105221 (CVE-2026-102271)

    Vulnerability from osv_azurelinux – Published: 2026-09-28 21:17 – Updated: 2026-11-01 07:13 – Source website
    VLAI
    Summary
    CVE-2026-102271 affecting package python-jwt for versions less than 2.15.1-1
    Details

    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 shared verification key. As a result, PyJWT uses public DER bytes 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.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.15.1-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.15.1-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "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 shared verification key. As a result, PyJWT uses public DER bytes 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.",
      "id": "AZL-105221",
      "modified": "2026-11-01T07:13:08Z",
      "published": "2026-09-28T21:17:15Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-102271"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-102271 affecting package python-jwt for versions less than 2.15.1-1",
      "upstream": [
        "CVE-2026-102271"
      ]
    }

    AZL-104991 (CVE-2026-102268)

    Vulnerability from osv_azurelinux – Published: 2026-09-28 21:17 – Updated: 2026-11-01 07:13 – Source website
    VLAI
    Summary
    CVE-2026-102268 affecting package python-jwt for versions less than 2.15.1-1
    Details

    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.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.15.1-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.15.1-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "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.",
      "id": "AZL-104991",
      "modified": "2026-11-01T07:13:08Z",
      "published": "2026-09-28T21:17:14Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-102268"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-102268 affecting package python-jwt for versions less than 2.15.1-1",
      "upstream": [
        "CVE-2026-102268"
      ]
    }

    AZL-104988 (CVE-2026-102270)

    Vulnerability from osv_azurelinux – Published: 2026-09-28 21:17 – Updated: 2026-11-01 07:13 – Source website
    VLAI
    Summary
    CVE-2026-102270 affecting package python-jwt for versions less than 2.15.1-1
    Details

    PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT is_pem_format is affected because lazy PEM regular expression backtracks extensively. This occurs when a certificate-like input contains repeated BEGIN markers without a matching END marker. As a result, is_pem_format performs unbounded backtracking while searching for a PEM end marker. Consequently, an attacker can cause intensive CPU consumption. This issue is fixed in version 2.14.0.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.15.1-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.15.1-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT is_pem_format is affected because lazy PEM regular expression backtracks extensively. This occurs when a certificate-like input contains repeated BEGIN markers without a matching END marker. As a result, is_pem_format performs unbounded backtracking while searching for a PEM end marker. Consequently, an attacker can cause intensive CPU consumption. This issue is fixed in version 2.14.0.",
      "id": "AZL-104988",
      "modified": "2026-11-01T07:13:08Z",
      "published": "2026-09-28T21:17:14Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-102270"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-102270 affecting package python-jwt for versions less than 2.15.1-1",
      "upstream": [
        "CVE-2026-102270"
      ]
    }

    AZL-104985 (CVE-2026-102269)

    Vulnerability from osv_azurelinux – Published: 2026-09-28 21:17 – Updated: 2026-11-01 07:13 – Source website
    VLAI
    Summary
    CVE-2026-102269 affecting package python-jwt for versions less than 2.15.1-1
    Details

    PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT signature segment is affected because signature segment decoding accepts characters outside the canonical Base64URL representation. This occurs when non-Base64URL characters are appended to a valid compact JWS signature segment. As a result, base64url_decode produces the same signature bytes for different serialized segments. Consequently, raw-token revocation checks can fail to recognize an equivalent modified token. This issue is fixed in version 2.14.0.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.15.1-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.15.1-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT signature segment is affected because signature segment decoding accepts characters outside the canonical Base64URL representation. This occurs when non-Base64URL characters are appended to a valid compact JWS signature segment. As a result, base64url_decode produces the same signature bytes for different serialized segments. Consequently, raw-token revocation checks can fail to recognize an equivalent modified token. This issue is fixed in version 2.14.0.",
      "id": "AZL-104985",
      "modified": "2026-11-01T07:13:08Z",
      "published": "2026-09-28T21:17:14Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-102269"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-102269 affecting package python-jwt for versions less than 2.15.1-1",
      "upstream": [
        "CVE-2026-102269"
      ]
    }

    AZL-105230 (CVE-2026-102265)

    Vulnerability from osv_azurelinux – Published: 2026-09-28 21:17 – Updated: 2026-11-01 07:13 – Source website
    VLAI
    Summary
    CVE-2026-102265 affecting package python-jwt for versions less than 2.15.1-1
    Details

    PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, PyJWS._load in jwt/api_jws.py is affected because parser catches ValueError but not RecursionError. This occurs when a deeply nested token header reaches json.loads. As a result, RecursionError escapes the documented PyJWT error hierarchy. Consequently, an unauthenticated malformed token can cause a request-level failure and HTTP 500. This issue is fixed in version 2.14.0.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.15.1-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.15.1-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, PyJWS._load in jwt/api_jws.py is affected because parser catches ValueError but not RecursionError. This occurs when a deeply nested token header reaches json.loads. As a result, RecursionError escapes the documented PyJWT error hierarchy. Consequently, an unauthenticated malformed token can cause a request-level failure and HTTP 500. This issue is fixed in version 2.14.0.",
      "id": "AZL-105230",
      "modified": "2026-11-01T07:13:08Z",
      "published": "2026-09-28T21:17:14Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-102265"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-102265 affecting package python-jwt for versions less than 2.15.1-1",
      "upstream": [
        "CVE-2026-102265"
      ]
    }

    AZL-105239 (CVE-2026-102266)

    Vulnerability from osv_azurelinux – Published: 2026-09-28 21:17 – Updated: 2026-11-01 07:13 – Source website
    VLAI
    Summary
    CVE-2026-102266 affecting package python-jwt for versions less than 2.15.1-1
    Details

    PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, HMACAlgorithm.from_jwk is affected because PyJWK verification path used the decoded key without applying prepare_key validation. This occurs when a trusted JWK Set contains an oct entry with an empty k value. As a result, an attacker signs an HMAC token with the same zero-length key accepted by PyJWT. Consequently, forged token can carry arbitrary authenticated claims. This issue is fixed in version 2.14.0.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.15.1-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.15.1-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, HMACAlgorithm.from_jwk is affected because PyJWK verification path used the decoded key without applying prepare_key validation. This occurs when a trusted JWK Set contains an oct entry with an empty k value. As a result, an attacker signs an HMAC token with the same zero-length key accepted by PyJWT. Consequently, forged token can carry arbitrary authenticated claims. This issue is fixed in version 2.14.0.",
      "id": "AZL-105239",
      "modified": "2026-11-01T07:13:08Z",
      "published": "2026-09-28T21:17:14Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-102266"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-102266 affecting package python-jwt for versions less than 2.15.1-1",
      "upstream": [
        "CVE-2026-102266"
      ]
    }

    AZL-104979 (CVE-2026-102267)

    Vulnerability from osv_azurelinux – Published: 2026-09-28 21:17 – Updated: 2026-11-01 07:13 – Source website
    VLAI
    Summary
    CVE-2026-102267 affecting package python-jwt for versions less than 2.15.1-1
    Details

    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.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.15.1-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.15.1-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "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.",
      "id": "AZL-104979",
      "modified": "2026-11-01T07:13:08Z",
      "published": "2026-09-28T21:17:14Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-102267"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-102267 affecting package python-jwt for versions less than 2.15.1-1",
      "upstream": [
        "CVE-2026-102267"
      ]
    }

    AZL-105218 (CVE-2026-101918)

    Vulnerability from osv_azurelinux – Published: 2026-09-28 21:17 – Updated: 2026-11-01 07:13 – Source website
    VLAI
    Summary
    CVE-2026-101918 affecting package python-jwt for versions less than 2.15.1-1
    Details

    PyJWT is a Python implementation of JSON Web Token standards. From 2.0.0a1 until 2.15.0, PyJWT PyJWKClient.get_signing_key_from_jwt is affected because payload parser catches ValueError but not RecursionError. This occurs when an attacker-controlled recursively nested payload reaches json.loads. As a result, documented PyJWT exception handling does not contain the failure. Consequently, an unauthenticated request can raise an exception that may produce an HTTP 500 response. The advisory-defined affected implementation also includes jwt/api_jwt.py, verify_signature=False. This issue is fixed in version 2.15.0.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.15.1-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.15.1-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a Python implementation of JSON Web Token standards. From 2.0.0a1 until 2.15.0, PyJWT PyJWKClient.get_signing_key_from_jwt is affected because payload parser catches ValueError but not RecursionError. This occurs when an attacker-controlled recursively nested payload reaches json.loads. As a result, documented PyJWT exception handling does not contain the failure. Consequently, an unauthenticated request can raise an exception that may produce an HTTP 500 response. The advisory-defined affected implementation also includes jwt/api_jwt.py, verify_signature=False. This issue is fixed in version 2.15.0.",
      "id": "AZL-105218",
      "modified": "2026-11-01T07:13:08Z",
      "published": "2026-09-28T21:17:13Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-101918"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-101918 affecting package python-jwt for versions less than 2.15.1-1",
      "upstream": [
        "CVE-2026-101918"
      ]
    }

    AZL-104982 (CVE-2026-101917)

    Vulnerability from osv_azurelinux – Published: 2026-09-28 21:17 – Updated: 2026-11-01 07:13 – Source website
    VLAI
    Summary
    CVE-2026-101917 affecting package python-jwt for versions less than 2.15.1-1
    Details

    PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT get_signing_key_from_jwt is affected because unknown kid misses force refreshes without a negative cache or minimum refresh interval. This occurs when unauthenticated tokens repeatedly use the same unknown kid or varying kid values absent from the cached JWKS. As a result, each cache miss causes PyJWKClient to refresh the JWKS. Consequently, attacker traffic can amplify outbound requests to the configured JWKS endpoint. This issue is fixed in version 2.14.0.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.15.1-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.15.1-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT get_signing_key_from_jwt is affected because unknown kid misses force refreshes without a negative cache or minimum refresh interval. This occurs when unauthenticated tokens repeatedly use the same unknown kid or varying kid values absent from the cached JWKS. As a result, each cache miss causes PyJWKClient to refresh the JWKS. Consequently, attacker traffic can amplify outbound requests to the configured JWKS endpoint. This issue is fixed in version 2.14.0.",
      "id": "AZL-104982",
      "modified": "2026-11-01T07:13:08Z",
      "published": "2026-09-28T21:17:13Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-101917"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-101917 affecting package python-jwt for versions less than 2.15.1-1",
      "upstream": [
        "CVE-2026-101917"
      ]
    }

    AZL-93033 (CVE-2026-48526)

    Vulnerability from osv_azurelinux – Published: 2026-05-28 16:16 – Updated: 2026-08-03 18:46 – Source website
    VLAI
    Summary
    CVE-2026-48526 affecting package python-jwt for versions less than 2.13.0-1
    Details

    PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, when the verifier is decoding JSON Web Tokens, while supporting both asymmetric and HMAC algorithms, the library does not validate use of JSON Web Keys in HMAC algorithm, allowing attacker to use the issuer public key as the secret key for HMAC algorithm. This vulnerability is fixed in 2.13.0.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.13.0-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.13.0-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, when the verifier is decoding JSON Web Tokens, while supporting both asymmetric and HMAC algorithms, the library does not validate use of JSON Web Keys in HMAC algorithm, allowing attacker to use the issuer public key as the secret key for HMAC algorithm. This vulnerability is fixed in 2.13.0.",
      "id": "AZL-93033",
      "modified": "2026-08-03T18:46:15Z",
      "published": "2026-05-28T16:16:29Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-48526"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-48526 affecting package python-jwt for versions less than 2.13.0-1",
      "upstream": [
        "CVE-2026-48526"
      ]
    }

    AZL-93027 (CVE-2026-48524)

    Vulnerability from osv_azurelinux – Published: 2026-05-28 16:16 – Updated: 2026-08-03 18:46 – Source website
    VLAI
    Summary
    CVE-2026-48524 affecting package python-jwt for versions less than 2.13.0-1
    Details

    PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, PyJWKClient.get_signing_key() forces a fresh HTTP request to the JWKS endpoint for every JWT with an unknown kid value, with no rate limiting. Since kid comes from the unverified token header, an attacker can trigger unlimited outbound requests. The vulnerability surfaces only when a JWKS fetch fails; an attacker can attempt to provoke that with sustained unknown-kid traffic, but the outcome depends on upstream JWKS-endpoint behavior (rate limiting, transient errors) which is beyond the attacker's control. This vulnerability is fixed in 2.13.0.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.13.0-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.13.0-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, PyJWKClient.get_signing_key() forces a fresh HTTP request to the JWKS endpoint for every JWT with an unknown kid value, with no rate limiting. Since kid comes from the unverified token header, an attacker can trigger unlimited outbound requests. The vulnerability surfaces only when a JWKS fetch fails; an attacker can attempt to provoke that with sustained unknown-kid traffic, but the outcome depends on upstream JWKS-endpoint behavior (rate limiting, transient errors) which is beyond the attacker\u0027s control. This vulnerability is fixed in 2.13.0.",
      "id": "AZL-93027",
      "modified": "2026-08-03T18:46:15Z",
      "published": "2026-05-28T16:16:29Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-48524"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-48524 affecting package python-jwt for versions less than 2.13.0-1",
      "upstream": [
        "CVE-2026-48524"
      ]
    }

    AZL-93036 (CVE-2026-48522)

    Vulnerability from osv_azurelinux – Published: 2026-05-28 16:16 – Updated: 2026-08-03 18:46 – Source website
    VLAI
    Summary
    CVE-2026-48522 affecting package python-jwt for versions less than 2.13.0-1
    Details

    PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, PyJWKClient passes its uri argument directly to urllib.request.urlopen() which uses Python stdlib's default OpenerDirector registering HTTPHandler, HTTPSHandler, FTPHandler, FileHandler, and DataHandler. There is currently no documented option to restrict which schemes PyJWKClient will fetch. If an application's jku URL ingestion path accepts attacker-influenced URLs (e.g., from JWT header, configuration file, OAuth flow parameter), the attacker can cause PyJWKClient to read arbitrary local files via file:// (SSRF on local filesystem), cause PyJWKClient to attempt FTP / data-URI fetches (broader SSRF surface), or forge tokens that PyJWT verifies as valid. The library does not directly return non-HTTP(S) URI contents to the attacker; the chained "plant a JWKS to forge tokens" scenario described in the original report requires additional application-layer flaws (attacker write access to a filesystem path, untrusted jku derivation) that this fix does not address. This vulnerability is fixed in 2.13.0.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.13.0-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.13.0-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, PyJWKClient passes its uri argument directly to urllib.request.urlopen() which uses Python stdlib\u0027s default OpenerDirector registering HTTPHandler, HTTPSHandler, FTPHandler, FileHandler, and DataHandler. There is currently no documented option to restrict which schemes PyJWKClient will fetch. If an application\u0027s jku URL ingestion path accepts attacker-influenced URLs (e.g., from JWT header, configuration file, OAuth flow parameter), the attacker can cause PyJWKClient to read arbitrary local files via file:// (SSRF on local filesystem), cause PyJWKClient to attempt FTP / data-URI fetches (broader SSRF surface), or forge tokens that PyJWT verifies as valid. The library does not directly return non-HTTP(S) URI contents to the attacker; the chained \"plant a JWKS to forge tokens\" scenario described in the original report requires additional application-layer flaws (attacker write access to a filesystem path, untrusted jku derivation) that this fix does not address. This vulnerability is fixed in 2.13.0.",
      "id": "AZL-93036",
      "modified": "2026-08-03T18:46:15Z",
      "published": "2026-05-28T16:16:29Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-48522"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-48522 affecting package python-jwt for versions less than 2.13.0-1",
      "upstream": [
        "CVE-2026-48522"
      ]
    }

    AZL-93042 (CVE-2026-48525)

    Vulnerability from osv_azurelinux – Published: 2026-05-28 16:16 – Updated: 2026-08-03 18:46 – Source website
    VLAI
    Summary
    CVE-2026-48525 affecting package python-jwt for versions less than 2.13.0-1
    Details

    PyJWT is a JSON Web Token implementation in Python. From 2.8.0 to 2.12.1, when verifying detached JWS tokens using the unencoded-payload option ("b64": false, RFC 7797), PyJWT performs Base64URL decoding of the compact-serialization payload segment before enforcing the detached-payload rules. For b64=false, PyJWT later discards that decoded payload and replaces it with the caller-provided detached_payload. In practice, this turns the middle segment into an attacker-controlled “work amplifier”: a remote client can supply an arbitrarily large Base64URL payload segment that forces CPU work + memory allocations even if the signature is invalid. This creates an unauthenticated DoS vector against any endpoint that verifies detached JWS using PyJWT. This vulnerability is fixed in 2.13.0.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.13.0-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.13.0-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a JSON Web Token implementation in Python. From 2.8.0 to 2.12.1, when verifying detached JWS tokens using the unencoded-payload option (\"b64\": false, RFC 7797), PyJWT performs Base64URL decoding of the compact-serialization payload segment before enforcing the detached-payload rules. For b64=false, PyJWT later discards that decoded payload and replaces it with the caller-provided detached_payload. In practice, this turns the middle segment into an attacker-controlled \u201cwork amplifier\u201d: a remote client can supply an arbitrarily large Base64URL payload segment that forces CPU work + memory allocations even if the signature is invalid. This creates an unauthenticated DoS vector against any endpoint that verifies detached JWS using PyJWT. This vulnerability is fixed in 2.13.0.",
      "id": "AZL-93042",
      "modified": "2026-08-03T18:46:15Z",
      "published": "2026-05-28T16:16:29Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-48525"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-48525 affecting package python-jwt for versions less than 2.13.0-1",
      "upstream": [
        "CVE-2026-48525"
      ]
    }

    AZL-93030 (CVE-2026-32597)

    Vulnerability from osv_azurelinux – Published: 2026-03-13 19:55 – Updated: 2026-08-03 18:46 – Source website
    VLAI
    Summary
    CVE-2026-32597 affecting package python-jwt for versions less than 2.13.0-1
    Details

    PyJWT is a JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array listing extensions that PyJWT does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirement in the RFC. This vulnerability is fixed in 2.12.0.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:3 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.13.0-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:3",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.13.0-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does not validate the crit (Critical) Header Parameter defined in RFC 7515 \u00a74.1.11. When a JWS token contains a crit array listing extensions that PyJWT does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirement in the RFC. This vulnerability is fixed in 2.12.0.",
      "id": "AZL-93030",
      "modified": "2026-08-03T18:46:15Z",
      "published": "2026-03-13T19:55:09Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32597"
        }
      ],
      "schema_version": "1.7.4",
      "summary": "CVE-2026-32597 affecting package python-jwt for versions less than 2.13.0-1",
      "upstream": [
        "CVE-2026-32597"
      ]
    }

    AZL-11032 (CVE-2022-39227)

    Vulnerability from osv_azurelinux – Published: 2022-09-23 07:15 – Updated: 2022-09-28 00:00 – Source website
    VLAI
    Summary
    CVE-2022-39227 affecting package python-jwt for versions less than 2.4.0-2
    Details

    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.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:2 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.4.0-2 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:2",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.4.0-2"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "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\u0027s identities, hijack their sessions, or bypass authentication. Users should upgrade to version 3.3.4. There are no known workarounds.",
      "id": "AZL-11032",
      "modified": "2022-09-28T00:00:00Z",
      "published": "2022-09-23T07:15:09Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-39227"
        }
      ],
      "schema_version": "1.7.4",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
          "type": "CVSS_V3"
        }
      ],
      "summary": "CVE-2022-39227 affecting package python-jwt for versions less than 2.4.0-2",
      "upstream": [
        "CVE-2022-39227"
      ]
    }

    AZL-9852 (CVE-2022-29217)

    Vulnerability from osv_azurelinux – Published: 2022-05-24 15:15 – Updated: 2022-06-17 08:10 – Source website
    VLAI
    Summary
    CVE-2022-29217 affecting package python-jwt for versions less than 2.4.0-1
    Details

    PyJWT is a Python implementation of RFC 7519. PyJWT supports multiple different JWT signing algorithms. With JWT, an attacker submitting the JWT token can choose the used signing algorithm. The PyJWT library requires that the application chooses what algorithms are supported. The application can specify jwt.algorithms.get_default_algorithms() to get support for all algorithms, or specify a single algorithm. The issue is not that big as algorithms=jwt.algorithms.get_default_algorithms() has to be used. Users should upgrade to v2.4.0 to receive a patch for this issue. As a workaround, always be explicit with the algorithms that are accepted and expected when decoding.

    Upstream
    References
    Impacted products
    Ecosystem Package Version
    Azure Linux:2 python-jwt
    pkg:rpm/azure-linux/python-jwt
    Affected: < 2.4.0-1 (ecosystem)

    {
      "affected": [
        {
          "package": {
            "ecosystem": "Azure Linux:2",
            "name": "python-jwt",
            "purl": "pkg:rpm/azure-linux/python-jwt"
          },
          "ranges": [
            {
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "2.4.0-1"
                }
              ],
              "type": "ECOSYSTEM"
            }
          ]
        }
      ],
      "details": "PyJWT is a Python implementation of RFC 7519. PyJWT supports multiple different JWT signing algorithms. With JWT, an attacker submitting the JWT token can choose the used signing algorithm. The PyJWT library requires that the application chooses what algorithms are supported. The application can specify `jwt.algorithms.get_default_algorithms()` to get support for all algorithms, or specify a single algorithm. The issue is not that big as `algorithms=jwt.algorithms.get_default_algorithms()` has to be used. Users should upgrade to v2.4.0 to receive a patch for this issue. As a workaround, always be explicit with the algorithms that are accepted and expected when decoding.",
      "id": "AZL-9852",
      "modified": "2022-06-17T08:10:20Z",
      "published": "2022-05-24T15:15:07Z",
      "references": [
        {
          "type": "WEB",
          "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-29217"
        }
      ],
      "schema_version": "1.7.4",
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
          "type": "CVSS_V3"
        }
      ],
      "summary": "CVE-2022-29217 affecting package python-jwt for versions less than 2.4.0-1",
      "upstream": [
        "CVE-2022-29217"
      ]
    }