<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T06:29:30.677156+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/cve-2026-48525</id>
    <title>CVE-2026-48525 — PyJWT: Unauthenticated DoS via unbounded Base64URL decoding of unused payload segment in b64=false detached JWS</title>
    <updated>2026-11-21T06:29:30.679247+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> jpadilla pyjwt</p>
<p>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.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/cve-2026-48525"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/usn-8823-1</id>
    <title>USN-8823-1 — pyjwt vulnerabilities</title>
    <updated>2026-11-21T06:29:30.679322+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: pyjwt, Ubuntu:Pro:18.04:LTS: pyjwt, Ubuntu:Pro:20.04:LTS: pyjwt, Ubuntu:22.04:LTS: pyjwt, Ubuntu:24.04:LTS: pyjwt, Ubuntu:26.04:LTS: pyjwt</p>
<p>It was discovered that PyJWT incorrectly handled certain URIs when using
PyJWKClient. A remote attacker could possibly use this issue to perform
server-side request forgery (SSRF) or expose sensitive local files.
This issue only affected Ubuntu 22.04 LTS, Ubuntu 24.04 LTS and Ubuntu
26.04 LTS. (CVE-2026-48522)</p>
<p>It was discovered that PyJWT incorrectly verified cryptographic signatures
when decoding tokens with PyJWK keys. A remote attacker could possibly
use this issue to bypass signature verification and forge valid JSON Web
Tokens. This issue only affected Ubuntu 26.04 LTS. (CVE-2026-48523)</p>
<p>It was discovered that PyJWT incorrectly handled unknown key identifiers
in PyJWKClient. A remote attacker could possibly use this issue to cause
PyJWT to make excessive network requests, resulting in a denial of service.
This issue only affected Ubuntu 24.04 LTS and Ubuntu 26.04 LTS.
(CVE-2026-48524)</p>
<p>It was discovered that PyJWT incorrectly handled payload decoding during
detached JWS token verification. A remote attacker could possibly use
this issue to cause PyJWT to consume excessive resources, resulting in
a denial of service. This issue only affected Ubuntu 24.04 LTS and
Ubuntu 26.04 LTS. (CVE-2026-48525)</p>
<p>It was discovered that PyJWT incorrectly validated JSON Web Keys when
decoding tokens with both HMAC and asymmetric algorithms enabled. A remote
attacker could possibly use this issue to forge valid tokens, resulting
in an authentication bypass. (CVE-2026-48526)</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/usn-8823-1"/>
  </entry>
</feed>
