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.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-3298 advisory.

    A flaw was found in PyJWT. A remote attacker can trigger a Denial of Service (DoS) through outbound     request amplification by submitting tokens containing unknown key identifiers. Because the library does     not cache lookup failures or enforce a minimum refresh interval when fetching signing keys, each invalid     key identifier forces a new request to the remote JSON Web Key Set (JWKS) server. This allows an attacker     to exhaust network resources and overwhelm the configured authentication endpoints. (CVE-2026-101917)

    A flaw was found in PyJWT. When processing a JSON Web Token (JWT) prior to signature verification, the     parser fails to properly handle deeply nested data, leading to an unhandled recursion error. A remote     unauthenticated attacker could exploit this flaw by submitting a specially crafted token, causing the     application to raise an unexpected server exception and resulting in a Denial of Service (DoS).
    (CVE-2026-101918)

    A flaw was found in pyjwt. A remote attacker can forge authentication tokens and bypass security controls     by signing tokens with an empty key. When verifying tokens against a JSON Web Key (JWK) set that contains     an empty Hash-based Message Authentication Code (HMAC) key, the library fails to enforce key-length     validation. This allows an attacker to generate valid tokens carrying arbitrary claims to gain     unauthorized access. (CVE-2026-102266)

    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 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. (CVE-2026-102271)

    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. (CVE-2026-102272)

    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. (CVE-2026-102273)

    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. (CVE-2026-102275)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2026:87004 advisory.

    Red Hat Ansible Automation Platform provides an enterprise framework for building, deploying and managing     IT automation at scale. IT Managers can provide top-down guidelines on how automation is applied to     individual teams, while automation developers retain the freedom to write tasks that leverage existing     knowledge without the overhead. Ansible Automation Platform makes it possible for users across an     organization to share, vet, and manage automation content by means of a simple, powerful, and agentless     language.

    Security Fix(es):

    * automation-gateway: authorization bypass via workload identity token forgery (CVE-2026-94416)
    * automation-platform-ui: proxy-addr vulnerable to IP spoofing via IPv4-mapped IPv6 trust subnet     (CVE-2026-90711)
    * automation-platform-ui: compression: Denial of Service via memory leak on premature response close     (CVE-2026-87776)
    * automation-platform-ui: fflate: Denial of Service via crafted ZIP archives (CVE-2026-45820)
    * python3.12-pulpcore: file:// scheme allowlist bypass in content upload file_url field enables arbitrary     file read and Pulp Container registry signing key theft (CVE-2026-90959)
    * python3.12-pyjwt: Verification key substitution via unvalidated JWKS redirects (CVE-2026-102267)
    * python3.12-pyjwt: Token forgery via improper Unicode byte-order mark handling (CVE-2026-102272)
    * python3.12-pyjwt: Authentication bypass via empty HMAC key acceptance (CVE-2026-102266)
    * python3.12-pyjwt: Authentication bypass via acceptance of DER public keys as HMAC secrets     (CVE-2026-102271)
    * python3.12-pyjwt: Token forgery via acceptance of public JWK containers as HMAC secrets     (CVE-2026-102273)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    For details about this release, refer to the release notes listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2026-102273)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2026-102273)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
371882	Amazon Linux 2023 : python3-jwt, python3-jwt+crypto (ALAS2023-2026-3298)	Nessus	Amazon Linux Local Security Checks	Local	critical
370142	RHEL 9 : Red Hat Ansible Automation Platform 2.6 Product Security and Bug Fix Update (Important) (RHSA-2026:87004)	Nessus	Red Hat Local Security Checks	Local	high
471618	Echo: pyjwt: security update to 2.14.0	Tenable Cloud Security	Echo Local Security Checks	Local	high
471618	Echo: pyjwt: security update to 2.14.0	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	high
351182	Linux Distros Unpatched Vulnerability : CVE-2026-102273	Nessus	Misc.	Local	high

Detections

Analytics

CVE-2026-102273

high

Tenable Plugins

critical

high

high

high

high