<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T19:45:25.370352+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2026-48522</id>
    <title>CVE-2026-48522 — PyJWKClient: missing scheme allowlist enables SSRF + token forgery via file://, ftp://, data: schemes</title>
    <updated>2026-09-30T19:45:25.373842+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. 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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-48522"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/usn-8823-1</id>
    <title>USN-8823-1 — pyjwt vulnerabilities</title>
    <updated>2026-09-30T19:45:25.373997+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://vulnerability.circl.lu/vuln/usn-8823-1"/>
  </entry>
</feed>
