<?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-21T10:35:05.401811+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/alsa-2026:12176</id>
    <title>ALSA-2026:12176 — Important: fence-agents security update</title>
    <updated>2026-11-21T10:35:05.450576+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:8: fence-agents-aliyun, AlmaLinux:8: fence-agents-all, AlmaLinux:8: fence-agents-amt-ws, AlmaLinux:8: fence-agents-apc, AlmaLinux:8: fence-agents-apc-snmp, AlmaLinux:8: fence-agents-aws, AlmaLinux:8: fence-agents-azure-arm, AlmaLinux:8: fence-agents-bladecenter, AlmaLinux:8: fence-agents-brocade, AlmaLinux:8: fence-agents-cisco-mds and 38 more</p>
<p>The fence-agents packages provide a collection of scripts for handling remote power management for cluster devices. They allow failed or unreachable nodes to be forcibly restarted and removed from the cluster.</p>
<p>Security Fix(es):</p>
<p>* cryptography: cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves (CVE-2026-26007)
  * pyjwt: PyJWT accepts unknown `crit` header extensions (RFC 7515 ?4.1.11 MUST violation) (CVE-2026-32597)
  * pyasn1: pyasn1 Vulnerable to Denial of Service via Unbounded Recursion (CVE-2026-30922)</p>
<p>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.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/alsa-2026:12176"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-32597</id>
    <title>BELL-CVE-2026-32597</title>
    <updated>2026-11-21T10:35:05.450657+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:25: py3-jwt, Alpaquita:stream: py3-jwt</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2026-32597"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/brew-azure-cli-cve-2026-32597</id>
    <title>BREW-azure-cli-CVE-2026-32597 — PyJWT accepts unknown `crit` header extensions</title>
    <updated>2026-11-21T10:35:05.450678+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: azure-cli</p>
<p>## Summary</p>
<p>PyJWT does not validate the `crit` (Critical) Header Parameter defined in
RFC 7515 §4.1.11. When a JWS token contains a `crit` array listing
extensions that PyJWT does not understand, the library accepts the token
instead of rejecting it. This violates the **MUST** requirement in the RFC.</p>
<p>This is the same class of vulnerability as CVE-2025-59420 (Authlib),
which received CVSS 7.5 (HIGH).</p>
<p>---</p>
<p>## RFC Requirement</p>
<p>RFC 7515 §4.1.11:</p>
<p>&gt; The "crit" (Critical) Header Parameter indicates that extensions to this
&gt; specification and/or [JWA] are being used that **MUST** be understood and
&gt; processed. [...] If any of the listed extension Header Parameters are
&gt; **not understood and supported** by the recipient, then the **JWS is invalid**.</p>
<p>---</p>
<p>## Proof of Concept</p>
<p>```python
import jwt  # PyJWT 2.8.0
import hmac, hashlib, base64, json</p>
<p># Construct token with unknown critical extension
header = {"alg": "HS256", "crit": ["x-custom-policy"], "x-custom-policy": "require-mfa"}
payload = {"sub": "attacker", "role": "admin"}</p>
<p>def b64url(data):
    return base64.urlsafe_b64encode(data).rstrip(b"=").decode()</p>
<p>h = b64url(json.dumps(header, separators=(",", ":")).encode())
p = b64url(json.dumps(payload, separators=(",", ":")).encode())
sig = b64url(hmac.new(b"secret", f"{h}.{p}".encode(), hashlib.sha256).digest())
token = f"{h}.{p}.{sig}"</p>
<p># Should REJECT — x-custom-policy is not understood by PyJWT
try:
    result = jwt.decode(token, "secret", algorithms=["HS256"])
    print(f"AC…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/brew-azure-cli-cve-2026-32597"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0316</id>
    <title>certfr-2026-avi-0316 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
    <updated>2026-11-21T10:35:05.450721+00:00</updated>
    <content>certfr-2026-avi-0316</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0316"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/cleanstart-2026-aj13963</id>
    <title>CLEANSTART-2026-AJ13963 — Security fix for CVE-2026-32597 applied in: airflow-2 2.11.2-r1, airflow-3 3.1.8-r0, airflow-3 3.2.0-r0, jupyterhub-k8s…</title>
    <updated>2026-11-21T10:35:05.450735+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: airflow-2, CleanStart: airflow-3, CleanStart: jupyterhub-k8s-hub</p>
<p>CVE-2026-32597 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/cleanstart-2026-aj13963"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-3117</id>
    <title>OESA-2026-3117 — python-jwt security update</title>
    <updated>2026-11-21T10:35:05.450749+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP4: python-jwt, openEuler:24.03-LTS-SP1: python-jwt, openEuler:24.03-LTS-SP3: python-jwt, openEuler:24.03-LTS-SP4: python-jwt, openEuler:20.03-LTS-SP4: python-jwt</p>
<p>rm -f tests/test_jwks_client.py  -m pytest %endif

Security Fix(es):</p>
<p>PyJWT is a JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array listing extensions that PyJWT does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirement in the RFC. This vulnerability is fixed in 2.12.0.(CVE-2026-32597)</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-3117"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rlsa-2026:19355</id>
    <title>RLSA-2026:19355 — Important: fence-agents security update</title>
    <updated>2026-11-21T10:35:05.450773+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Rocky Linux:9: fence-agents-aliyun, Rocky Linux:9: fence-agents-all, Rocky Linux:9: fence-agents-aws, Rocky Linux:9: fence-agents-azure-arm, Rocky Linux:9: fence-agents-compute, Rocky Linux:9: fence-agents-debuginfo, Rocky Linux:9: fence-agents-debugsource, Rocky Linux:9: fence-agents-gce, Rocky Linux:9: fence-agents-kdump, Rocky Linux:9: fence-agents-kdump-debuginfo and 58 more</p>
<p>The fence-agents packages provide a collection of scripts for handling remote power management for cluster devices. They allow failed or unreachable nodes to be forcibly restarted and removed from the cluster.</p>
<p>Security Fix(es):</p>
<p>* cryptography: cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves (CVE-2026-26007)</p>
<p>* pyjwt: PyJWT accepts unknown `crit` header extensions (RFC 7515 ?4.1.11 MUST violation) (CVE-2026-32597)</p>
<p>* pyasn1: pyasn1 Vulnerable to Denial of Service via Unbounded Recursion (CVE-2026-30922)</p>
<p>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.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rlsa-2026:19355"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-32597</id>
    <title>UBUNTU-CVE-2026-32597</title>
    <updated>2026-11-21T10:35:05.450840+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:25.10: pyjwt</p>
<p>PyJWT is a JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array listing extensions that PyJWT does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirement in the RFC. This vulnerability is fixed in 2.12.0.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-32597"/>
  </entry>
</feed>
