<?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:31:36.765421+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:25902</id>
    <title>ALSA-2026:25902 — Important: fence-agents security update</title>
    <updated>2026-11-21T06:31:36.780198+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:10: fence-agents-amt-ws, AlmaLinux:10: fence-agents-apc, AlmaLinux:10: fence-agents-apc-snmp, AlmaLinux:10: fence-agents-bladecenter, AlmaLinux:10: fence-agents-brocade, AlmaLinux:10: fence-agents-cisco-mds, AlmaLinux:10: fence-agents-cisco-ucs, AlmaLinux:10: fence-agents-drac5, AlmaLinux:10: fence-agents-eaton-snmp, AlmaLinux:10: fence-agents-emerson and 26 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>* python-pyjwt: PyJWT: Authentication bypass due to forged JSON Web Tokens (CVE-2026-48526)</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:25902"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-48526</id>
    <title>BELL-CVE-2026-48526</title>
    <updated>2026-11-21T06:31:36.780262+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-48526"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/brew-azure-cli-cve-2026-48526</id>
    <title>BREW-azure-cli-CVE-2026-48526 — PyJWT: Public-key JWK accepted as HMAC secret enables forged HS256 tokens when mixed families are allowed</title>
    <updated>2026-11-21T06:31:36.780278+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: azure-cli</p>
<p>&gt; [!NOTE]
&gt; Exploitation requires a verifier configured with both symmetric and asymmetric algorithms in `algorithms=[…]` and a raw-JSON JWK as the `key=` argument, both contrary to documented usage, hence the High attack-complexity rating.</p>
<p>### Summary
When the verifier is decoding JSON Web Tokens, while supporting both asymmetric and HMAC algorithms, the library does not validate use of JSON Web Keys in HMAC algorithm, allowing attacker to use the issuer public key as the secret key for HMAC algorithm.</p>
<p>### Details
In JWT algorithm confusion attack, the verifier is mistakenly use of public key to be used as the shared secret in symmetric algorithms.
In pyjwt case, when the verifier is supporting both HMAC with other asymmetric algorithm and mistakenly using the public key of the issuer to verify the token as demonstrated in the following example:
  
`jws.decode(token, key=rsa_jwk_json, algorithms=["HS256","RS256"])) `</p>
<p>An attacker who specifies in the token header to use HMAC, will cause the verifier to accept the JWK as the secret key in HMAC algorithm. 
The attacker will be able to forge JWT signed with the public key of the issuer to impersonate any user.</p>
<p>If we look on current protections implemented in the library, at class HMACAlgorithm:</p>
<p>```
  def prepare_key(self, key: str | bytes) -&gt; bytes:
        key_bytes = force_bytes(key)</p>
<p>if is_pem_format(key_bytes) or is_ssh_key(key_bytes):
            raise InvalidKeyError(
                "The specified key is…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/brew-azure-cli-cve-2026-48526"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-1366</id>
    <title>certfr-2026-avi-1366 — De multiples vulnérabilités ont été découvertes dans les produits Splunk. Certaines d'entre elles permettent à un attaq…</title>
    <updated>2026-11-21T06:31:36.780320+00:00</updated>
    <content>certfr-2026-avi-1366</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-1366"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/cleanstart-2026-af67526</id>
    <title>Withdrawn: CLEANSTART-2026-AF67526 — Security fixes for CVE-2026-42304, CVE-2026-44307, CVE-2026-48522, CVE-2026-48523, CVE-2026-48524, CVE-2026-48525, CVE-…</title>
    <updated>2026-11-21T06:31:36.780330+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Withdrawn by the publisher.</strong></p>
<p><strong>Affected:</strong> CleanStart: jupyterhub-k8s-hub</p>
<p>Multiple security vulnerabilities affect the jupyterhub-k8s-hub package. These issues are resolved in later releases. See references for individual vulnerability details.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/cleanstart-2026-af67526"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rlsa-2026:25902</id>
    <title>RLSA-2026:25902 — Important: fence-agents security update</title>
    <updated>2026-11-21T06:31:36.780343+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Rocky Linux:10: fence-agents-common, Rocky Linux:10: fence-agents-redfish, Rocky Linux:10: fence-agents-debuginfo, Rocky Linux:10: fence-agents-kdump, Rocky Linux:10: fence-agents-debugsource, Rocky Linux:10: fence-agents-kubevirt, Rocky Linux:10: fence-agents-common-debuginfo, Rocky Linux:10: fence-agents-all, Rocky Linux:10: fence-agents-kdump-debuginfo, Rocky Linux:10: fence-agents-mpath and 57 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>* python-pyjwt: PyJWT: Authentication bypass due to forged JSON Web Tokens (CVE-2026-48526)</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:25902"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-48526</id>
    <title>UBUNTU-CVE-2026-48526</title>
    <updated>2026-11-21T06:31:36.780407+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, Ubuntu:26.04:LTS: pyjwt</p>
<p>PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, when the verifier is decoding JSON Web Tokens, while supporting both asymmetric and HMAC algorithms, the library does not validate use of JSON Web Keys in HMAC algorithm, allowing attacker to use the issuer public key as the secret key for HMAC algorithm. This vulnerability is fixed in 2.13.0.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-48526"/>
  </entry>
</feed>
