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

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

Linux/Unix 主机中安装的一个或多个程序包受到一个漏洞影响，而供应商没有提供补丁程序。

  - PyJWT 是 Python 中的 JSON Web Token 实现。从 2.8.0 to 2.12.1，当使用 unencoded-payload 选项（b64：false，RFC 7797）验证分离的 JWS 标记时，PyJWT 会在强制执行分离负载规则之前对压缩序列化负载段执行 Base64URL 解码。如果 b64=false，PyJWT 稍后会丢弃解码的负载，并将其替换为调用方提供的detached_payload。实际上，这会将中间段转变为由攻击者控制的工作放大器：远程客户端可提供任意大的 Base64URL 负载段，即使签名无效，该段也强制 CPU 工作 + 内存分配。这会针对使用 PyJWT 验证分离的 JWS 的任何端点创建未经身份验证的 DoS 向量。此漏洞已在 2.13.0 中修复。(CVE-2026-48525)

请注意，Nessus 依赖供应商报告的程序包是否存在进行判断。

Linux/Unix 主機上安裝了一個或多個受到弱點影響的套件，且供應商未提供可用的修補程式。

  - PyJWT 是 Python 中的 JSON Web 令牌實作。從 2.8.0 到 2.12.1，當使用 unencoded-payload 選項（b64：false，RFC 7797）驗證分離的 JWS 令牌時，PyJWT 會在強制執行分離有效負載規則之前對緊湊序列化有效負載段執行 Base64URL 解碼。對於 b64=false，PyJWT 稍後會捨棄該解碼的承載，並將其替換為呼叫者提供的detached_payload。在實踐中，這會將中間段變成攻擊者控制的工作放大器：遠端用戶端可以提供任意大的 Base64URL 有效負載段，即使簽章無效，也強制 CPU 工作 + 記憶體分配。這會針對使用 PyJWT 驗證分離 JWS 的任何端點建立未經驗證的 DoS 向量。此弱點已在 2.13.0 中修正。(CVE-2026-48525)

請注意，Nessus 依賴供應商報告的套件存在。

Linux/Unix ホストには、ベンダーが提供するパッチが利用できない脆弱性の影響を受ける複数のパッケージがインストールされています。

  - PyJWTは、PythonのJSON Webトークン実装です。2.8.0から2.12.1まで、unencoded-payloadオプション(b64:false、RFC 7797)を使用してデタッチされたJWSトークンを検証するとき、PyJWTはデタッチペイロードルールを適用する前に、コンパクトシリアル化ペイロードセグメントのBase64URLデコーディングを実行します。b64=falseの場合、PyJWTは後でそのデコードされたペイロードを破棄し、呼び出し元が用意したdetached_payloadと置き換えます。実際には、これにより中間セグメントが攻撃者が制御する作業アンプに変わります。リモートクライアントは、署名が無効であっても CPU 作業 + メモリ割り当てを強制する、任意の大きな Base64URL ペイロードセグメントを供給することが可能です。これは、PyJWT を使用してデタッチされた JWS を検証するエンドポイントに対して認証されていない DoS ベクトルを作成します。この脆弱性は 2.13.0 で修正されました。(CVE-2026-48525)

Nessus は、ベンダーによって報告されたパッケージの存在に依存していることに注意してください。

The remote SUSE Linux SLES16 / SLES_SAP16 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:22170-1 advisory.

    This update for python-PyJWT fixes the following issues

    - CVE-2026-48522: `PyJWKClient` passes URI arguments directly to `urllib.request.urlopen()` and allows for     SSRF and       token forgery (bsc#1266798).
    - CVE-2026-48523: verifier-side algorithm allow-list bypass when `jwt.decode()` or `jwt.decode_complete()`     are called       with a PyJWK key (bsc#1266799).
    - CVE-2026-48524: unlimited processing of JWTs with unknown kid values by `PyJWKClient.get_signing_key()`     leads to       unbounded JWKS endpoint requests and DoS (bsc#1266800).
    - CVE-2026-48525: unbounded Base64URL decoding of unused payload segment in `b64=false` detached JWS     allows for DoS       (bsc#1266801).
    - CVE-2026-48526: no validation of use of JSON Web Keys in HMAC algorithm when decoding JSON Web Tokens     allows for       forged HS256 tokens (bsc#1266802).

Tenable has extracted the preceding description block directly from the SUSE 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 version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2026:0427 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2026-48525:
    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.

    CVE-2026-48524:
    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.

    CVE-2026-48523:
    PyJWT is a JSON Web Token implementation in Python. From 2.9.0 to 2.12.1, there is a verifier-side     algorithm allow-list bypass when jwt.decode() or jwt.decode_complete() are called with a PyJWK key. The     token header alg is checked against the caller-supplied algorithms allow-list, but signature verification     is performed with the algorithm bound to the PyJWK object instead of the header algorithm. An attacker who     controls a registered JWK/JWKS private key can sign with a disallowed algorithm, advertise an allowed     algorithm in the JWT header, and still be accepted. The issue affects the documented     PyJWKClient.get_signing_key_from_jwt(...) flow. This vulnerability is fixed in 2.13.0.

    CVE-2026-48522:
    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.

Tenable has extracted the preceding description block directly from the Tencent 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.

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

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

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:2626-1 advisory.

    This update for python-PyJWT fixes the following issues

    - CVE-2026-48522: `PyJWKClient` passes URI arguments directly to `urllib.request.urlopen()` and allows for     SSRF and       token forgery (bsc#1266798).
    - CVE-2026-48523: verifier-side algorithm allow-list bypass when `jwt.decode()` or `jwt.decode_complete()`     are called       with a PyJWK key (bsc#1266799).
    - CVE-2026-48524: unlimited processing of JWTs with unknown kid values by `PyJWKClient.get_signing_key()`     leads to       unbounded JWKS endpoint requests and DoS (bsc#1266800).
    - CVE-2026-48525: unbounded Base64URL decoding of unused payload segment in `b64=false` detached JWS     allows for DoS       (bsc#1266801).
    - CVE-2026-48526: no validation of use of JSON Web Keys in HMAC algorithm when decoding JSON Web Tokens     allows for       forged HS256 tokens (bsc#1266802).

Tenable has extracted the preceding description block directly from the SUSE 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 SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:2627-1 advisory.

    This update for python-PyJWT fixes the following issues

    - CVE-2026-48522: `PyJWKClient` passes URI arguments directly to `urllib.request.urlopen()` and allows for     SSRF and       token forgery (bsc#1266798).
    - CVE-2026-48523: verifier-side algorithm allow-list bypass when `jwt.decode()` or `jwt.decode_complete()`     are called       with a PyJWK key (bsc#1266799).
    - CVE-2026-48525: unbounded Base64URL decoding of unused payload segment in `b64=false` detached JWS     allows for DoS       (bsc#1266801).
    - CVE-2026-48526: no validation of use of JSON Web Keys in HMAC algorithm when decoding JSON Web Tokens     allows for       forged HS256 tokens (bsc#1266802).

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

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
443265	SCA: security update for pyjwt (GHSA-w7vc-732c-9m39)	Tenable Cloud Security	SCA Checks	2026/6/16	2026/7/2	medium
443265	SCA: security update for pyjwt (GHSA-w7vc-732c-9m39)	Tenable Self-Hosted Container Security	SCA Checks	2026/6/16	2026/7/2	medium
317761	Linux Distros 未修补的漏洞：CVE-2026-48525	Nessus	Misc.	2026/5/29	2026/7/27	medium
317761	Linux Distros 未修補的弱點：CVE-2026-48525	Nessus	Misc.	2026/5/29	2026/7/27	medium
317761	Linux Distros のパッチ未適用の脆弱性: CVE-2026-48525	Nessus	Misc.	2026/5/29	2026/7/27	medium
322913	SUSE SLES16 Security Update : python-PyJWT (SUSE-SU-2026:22170-1)	Nessus	SuSE Local Security Checks	2026/6/26	2026/6/26	high
319736	TencentOS Server 4: python-jwt (TSSA-2026:0427)	Nessus	Tencent Local Security Checks	2026/6/8	2026/6/8	medium
317761	Linux Distros Unpatched Vulnerability : CVE-2026-48525	Nessus	Misc.	2026/5/29	2026/7/27	medium
323065	SUSE SLED15 / SLES15 Security Update : python-PyJWT (SUSE-SU-2026:2626-1)	Nessus	SuSE Local Security Checks	2026/6/26	2026/6/26	high
323028	SUSE SLED15 / SLES15 Security Update : python-PyJWT (SUSE-SU-2026:2627-1)	Nessus	SuSE Local Security Checks	2026/6/26	2026/6/26	high

检测

插件搜索

medium

medium

medium

medium

medium

high

medium

medium

high

high