<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-15T20:37:01.834593+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-101917</id>
    <title>CVE-2026-101917 — PyJWT: PyJWKClient still amplifies unauthenticated JWKS fetches on unknown kid values (incomplete fix of CVE-2026-48524)</title>
    <updated>2026-11-15T20:37:01.836358+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 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.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-101917"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/usn-8934-1</id>
    <title>USN-8934-1 — pyjwt vulnerabilities</title>
    <updated>2026-11-15T20:37:01.836426+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.10: pyjwt, Ubuntu:26.04:LTS: pyjwt</p>
<p>Kingsley Olukanni discovered that PyJWT did not properly handle unknown key
identifiers when retrieving signing keys. An attacker could possibly use
this issue to amplify requests to the configured key endpoint, resulting in
a denial of service. This issue only affected Ubuntu 22.04 LTS, Ubuntu
24.04 LTS, Ubuntu 26.04 LTS and Ubuntu 26.10. (CVE-2026-101917)</p>
<p>Ekalabya Ghosh discovered that PyJWT did not properly handle certain
recursively nested JSON payloads. An attacker could possibly use this issue
to cause an application to fail, resulting in a denial of service.
(CVE-2026-101918)</p>
<p>Pedram Hayati discovered that PyJWT did not properly handle malformed RSA
keys in a JSON Web Key Set. An attacker could possibly use this issue to
cause authentication failures or a denial of service. This issue only
affected Ubuntu 22.04 LTS, Ubuntu 24.04 LTS,  Ubuntu 26.04 LTS and Ubuntu
26.10. (CVE-2026-102274)</p>
<p>It was discovered that PyJWT did not properly validate certain OKP private
key components. An attacker could possibly use this issue to confuse the
identity of public and private keys, and use a stolen sender-constrained
token without the legitimate private key. This issue only affected Ubuntu
22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 26.04 LTS and Ubuntu 26.10.
(CVE-2026-102275)</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/usn-8934-1"/>
  </entry>
</feed>
