<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>RADAR — GitHub advisories — pip</title>
    <link>https://radar.trulysovereign.com</link>
    <atom:link href="https://radar.trulysovereign.com/feeds/source/github-advisories-pip.xml" rel="self" type="application/rss+xml"/>
    <description>Changes RADAR detected at GitHub advisories — pip.</description>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 19:19:18 GMT</lastBuildDate>
    <item>
      <title>AIT-GUI route chain allows unauthenticated Python execution</title>
      <link>https://radar.trulysovereign.com/items/342293b5-dd6a-480f-957e-bae6fb2c5452</link>
      <guid isPermaLink="false">342293b5-dd6a-480f-957e-bae6fb2c5452</guid>
      <pubDate>Sat, 21 Nov 2026 19:19:11 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>GitHub published GHSA-jrjx-9jjw-747m on 20 November 2026, rating CVE-2026-77309 high severity. The advisory states that a route chain in ait-gui allows unauthenticated Python execution in the server process. Version 2.5.1 patches the vulnerability.

Why it matters: An unauthenticated attacker can execute arbitrary Python code in the server process, achieving full remote code execution without credentials. Any exposed ait-gui instance running an unpatched version is compromised on contact.

What to do: Upgrade ait-gui to version 2.5.1 or later. If you cannot upgrade immediately, take the service offline or restrict network access to authenticated internal users only until patched.</description>
    </item>
    <item>
      <title>Mistune 3.3.3 and earlier: quadratic-time DoS in inline image parsing</title>
      <link>https://radar.trulysovereign.com/items/d35d0e29-a6c2-4032-989a-540b5d979eab</link>
      <guid isPermaLink="false">d35d0e29-a6c2-4032-989a-540b5d979eab</guid>
      <pubDate>Fri, 20 Nov 2026 07:21:49 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>GitHub published GHSA-ww7q-mxrj-5ffg on 19 November 2026, rating a denial-of-service vulnerability in mistune (CVE-2026-97699) as high severity. The flaw is in inline image parsing (precedence_scan) and bypasses not-is-image guards. First patched version: 3.3.4.

Why it matters: Mistune is a markdown parser in Python dependency trees. An attacker can trigger quadratic-time processing, causing the parser to hang or exhaust resources on crafted input.

What to do: Check whether mistune is in your dependency tree and whether you are running 3.3.3 or earlier. If so, update to 3.3.4.</description>
    </item>
    <item>
      <title>MCP Python SDK could send OAuth credentials to attacker-chosen server</title>
      <link>https://radar.trulysovereign.com/items/1add7a7a-43d4-432a-97b6-fe55e3b5c3d5</link>
      <guid isPermaLink="false">1add7a7a-43d4-432a-97b6-fe55e3b5c3d5</guid>
      <pubDate>Fri, 20 Nov 2026 07:21:35 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>GitHub published GHSA-qx49-fqc8-xw99 (CVE-2026-115563) on 19 November 2026, rating it high severity. The Model Context Protocol Python SDK mcp package allows an MCP server to choose the OAuth authorization server, enabling credential interception. Patched in mcp 1.30.0 and 2.2.0.

Why it matters: An application using the vulnerable SDK to authenticate with an MCP server can be tricked into sending OAuth credentials to an attacker-controlled authorization endpoint. The attacker gains the credentials and can impersonate the application.

What to do: Check whether you depend on mcp (Model Context Protocol Python SDK) at any version below 1.30.0 or 2.x below 2.2.0. If so, update to 1.30.0, 2.2.0 or later in this cycle.</description>
    </item>
    <item>
      <title>Mistune 3.3.3 and earlier vulnerable to quadratic-time DoS</title>
      <link>https://radar.trulysovereign.com/items/e5e47794-943e-4277-afed-734499be073f</link>
      <guid isPermaLink="false">e5e47794-943e-4277-afed-734499be073f</guid>
      <pubDate>Fri, 20 Nov 2026 07:21:26 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>GitHub published GHSA-phmp-hrw4-r36r on 19 November 2026, rating CVE-2026-97698 high severity. Mistune versions before 3.3.4 are vulnerable to quadratic-time denial of service through unbounded parenthesis scanning when parsing empty-label links. Version 3.3.4 patches the vulnerability.

Why it matters: An attacker can cause CPU exhaustion in any service that parses untrusted Markdown through mistune, including user-generated content, documentation sites, and API endpoints that accept Markdown input. The quadratic complexity means processing time grows exponentially with input size.

What to do: Upgrade mistune to 3.3.4. Check your dependency tree with `pip list | grep mistune` or `poetry show mistune` to confirm the installed version, as mistune is a transitive dependency in many Python Markdown toolchains.</description>
    </item>
    <item>
      <title>NLTK 3.10.3 and earlier allows local code execution via prover9/mace4 config</title>
      <link>https://radar.trulysovereign.com/items/fd177730-0f17-41d1-b548-32de03af008f</link>
      <guid isPermaLink="false">fd177730-0f17-41d1-b548-32de03af008f</guid>
      <pubDate>Fri, 20 Nov 2026 07:21:12 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>GitHub published GHSA-cc5r-64rf-75hg on 19 November 2026, rating CVE-2026-129234 high severity. NLTK versions before 3.10.4 use an untrusted search path in prover9/mace4 configuration, allowing local code execution through a relative binary_location value. Version 3.10.4 patches the vulnerability.

Why it matters: An attacker with local access can execute arbitrary code by placing a malicious binary in the search path before NLTK resolves the prover9 or mace4 binary location. This affects any deployment where NLTK's theorem proving components run with untrusted local users or in shared environments.

What to do: Upgrade nltk to 3.10.4 or later. If you cannot upgrade immediately, verify whether your code calls NLTK's prover9 or mace4 interfaces and restrict local access to systems running those components.</description>
    </item>
    <item>
      <title>django-docutils before 0.30.0 allows file disclosure, SSRF, and XSS</title>
      <link>https://radar.trulysovereign.com/items/9e8c70e0-7d41-4c19-914c-cee0aabc6d7f</link>
      <guid isPermaLink="false">9e8c70e0-7d41-4c19-914c-cee0aabc6d7f</guid>
      <pubDate>Fri, 20 Nov 2026 07:20:59 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>GitHub published GHSA-86mf-q4h5-69gp (CVE-2026-59988) on 20 November 2026, rating django-docutils high severity. Versions before 0.30.0 use unsafe Docutils defaults that enable local file disclosure, server-side request forgery, and stored cross-site scripting. Version 0.30.0 patches the vulnerability.

Why it matters: Applications using django-docutils to render user-supplied reStructuredText can leak local files to attackers, make requests to internal services, or store malicious scripts that execute in other users' browsers. All three attack vectors are exploitable through the same unsafe configuration.

What to do: Upgrade django-docutils to 0.30.0 or later. Check whether your application accepts reStructuredText input from users and passes it to django-docutils rendering functions.</description>
    </item>
    <item>
      <title>flyto-core 2.26.8 patches SSRF in http.paginate Link header handling</title>
      <link>https://radar.trulysovereign.com/items/c1de4d06-f963-45d7-a558-8543f14a55e6</link>
      <guid isPermaLink="false">c1de4d06-f963-45d7-a558-8543f14a55e6</guid>
      <pubDate>Fri, 20 Nov 2026 07:20:46 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>CVE-2026-77315 published 20 November 2026. flyto-core's http.paginate follows server-supplied next-page URLs from Link headers or cursors without revalidating the destination, enabling SSRF. First patched version is 2.26.8.

Why it matters: An attacker controlling a paginated API response can redirect http.paginate to internal endpoints, cloud metadata services, or other restricted targets your application can reach but should not query on external instruction.

What to do: Upgrade flyto-core to 2.26.8 or later. If you use http.paginate with untrusted APIs, verify you are running a vulnerable version before 2.26.8 and prioritize the update.</description>
    </item>
    <item>
      <title>Jupyter MCP Server unauthenticated routes allow backend hijack in standalone HTTP mode</title>
      <link>https://radar.trulysovereign.com/items/16bd8fa7-0e06-4bda-ab4a-7f60d0b992fb</link>
      <guid isPermaLink="false">16bd8fa7-0e06-4bda-ab4a-7f60d0b992fb</guid>
      <pubDate>Fri, 20 Nov 2026 07:20:37 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>GitHub published GHSA-24pw-rf5p-mgp7 (CVE-2026-77318) on 20 November 2026, rating it high severity. Jupyter MCP Server before version 1.0.3 exposes unauthenticated management routes that can hijack the Jupyter backend when deployed in standalone HTTP mode.

Why it matters: An attacker with network access to the management routes can take control of the Jupyter backend without authentication, compromising notebook execution environments and any data or credentials accessible to the runtime.

What to do: Update jupyter-mcp-server to version 1.0.3. If you run Jupyter MCP Server in standalone HTTP mode, verify whether management routes are exposed to untrusted networks and prioritize the update.</description>
    </item>
    <item>
      <title>mail-parser 4.6.0 and earlier vulnerable to ReDoS in header parsing</title>
      <link>https://radar.trulysovereign.com/items/bba1e449-40f1-4d48-ac81-24e3dcaa2c15</link>
      <guid isPermaLink="false">bba1e449-40f1-4d48-ac81-24e3dcaa2c15</guid>
      <pubDate>Tue, 17 Nov 2026 07:57:10 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>GitHub published GHSA-r7w7-vpq8-c5vv on 16 November 2026, rating mail-parser vulnerable to polynomial regular expression denial of service (ReDoS) during email header parsing. CVE-2026-129295 assigned. First patched version is 4.6.1.

Why it matters: An attacker can cause CPU exhaustion by sending crafted email headers, blocking the parser and any service that depends on it. Services that parse untrusted email are exposed.

What to do: Check whether you run mail-parser 4.6.0 or earlier. If so, update to 4.6.1.</description>
    </item>
    <item>
      <title>mail-parser 4.6.2 patches sender IP spoofing in get_server_ipaddress()</title>
      <link>https://radar.trulysovereign.com/items/954ceb2c-8653-418a-bf57-a371d981eec4</link>
      <guid isPermaLink="false">954ceb2c-8653-418a-bf57-a371d981eec4</guid>
      <pubDate>Tue, 17 Nov 2026 07:57:02 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>GitHub published GHSA-72px-j8gh-p79x on 16 November 2026, a high-severity advisory for CVE-2026-129297 in mail-parser. The vulnerability allows sender IP address spoofing in the get_server_ipaddress() function. Version 4.6.2 patches the issue.

Why it matters: Applications using mail-parser to extract or validate sender IP addresses can be deceived about message origin, bypassing IP-based access controls, allowlists, or audit trails that depend on accurate sender identification.

What to do: Check whether mail-parser is in your dependency tree and upgrade to 4.6.2 or later if you are running an affected version.</description>
    </item>
    <item>
      <title>aiohttp 3.14.4 patches DoS via URL-encoded form fields</title>
      <link>https://radar.trulysovereign.com/items/bfa1a038-ce29-48c4-86d9-55b5f5136f6d</link>
      <guid isPermaLink="false">bfa1a038-ce29-48c4-86d9-55b5f5136f6d</guid>
      <pubDate>Mon, 16 Nov 2026 22:03:32 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>GitHub published GHSA-xgw8-8ccx-rmqh on 16 November 2026, rating CVE-2026-128126 high severity. The vulnerability affects aiohttp versions before 3.14.4: too many URL-encoded form fields block the event loop, causing denial of service. Version 3.14.4 patches the issue.

Why it matters: An attacker can block the event loop by sending requests with excessive URL-encoded form fields, making the service unresponsive. Any Python service using aiohttp to handle untrusted HTTP requests is exposed.

What to do: Upgrade aiohttp to 3.14.4 or later. Check requirements files and deployed containers for aiohttp &lt; 3.14.4.</description>
    </item>
    <item>
      <title>aiohttp unbounded buffering in upgrade requests</title>
      <link>https://radar.trulysovereign.com/items/71d95938-2aad-4118-9ba3-094311c7e1e1</link>
      <guid isPermaLink="false">71d95938-2aad-4118-9ba3-094311c7e1e1</guid>
      <pubDate>Mon, 16 Nov 2026 22:03:23 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>GitHub published GHSA-pw86-h8fm-j323 (CVE-2026-128129) on 16 November 2026, rating a high-severity unbounded buffering vulnerability in aiohttp during upgrade request handling. First patched version is 3.14.4.

Why it matters: Unbounded buffering during request handling allows an attacker to exhaust memory by sending crafted upgrade requests, causing service degradation or denial of service in applications using affected aiohttp versions.

What to do: Check your dependency tree for aiohttp versions below 3.14.4. If present, update to 3.14.4 or later in this cycle.</description>
    </item>
    <item>
      <title>aiohttp 3.14.4 patches event loop stall in wildcard matching</title>
      <link>https://radar.trulysovereign.com/items/36a458c5-a4a6-40e8-9292-ad50776a866f</link>
      <guid isPermaLink="false">36a458c5-a4a6-40e8-9292-ad50776a866f</guid>
      <pubDate>Mon, 16 Nov 2026 22:03:15 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>GitHub published GHSA-jm3w-gw2p-xjfj on 16 November 2026, a high-severity advisory for CVE-2026-128124 in aiohttp. The vulnerability causes event loop stalls in add_domain() wildcard matching. First patched version is 3.14.4.

Why it matters: An attacker can stall the async event loop, blocking all concurrent requests and responses in the application. This is a denial of service vector in the core async runtime that affects any service using aiohttp's domain matching.

What to do: Upgrade aiohttp to 3.14.4 or later. Check requirements files and lock files for aiohttp dependencies below 3.14.4.</description>
    </item>
    <item>
      <title>aiohttp 3.14.4 patches DoS via concatenated compressed streams</title>
      <link>https://radar.trulysovereign.com/items/e73106cd-74dd-41fe-8f8f-216b7eb36cd5</link>
      <guid isPermaLink="false">e73106cd-74dd-41fe-8f8f-216b7eb36cd5</guid>
      <pubDate>Mon, 16 Nov 2026 22:03:05 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>GitHub published GHSA-h4cc-hm5h-fmm9 (CVE-2026-128131) on 16 November 2026, rating it high severity. aiohttp versions before 3.14.4 consume excessive CPU when processing concatenated compressed streams, creating a denial-of-service vector.

Why it matters: Services using aiohttp to handle HTTP requests can be forced into CPU exhaustion by a crafted payload, degrading or stopping availability. This affects any deployment where aiohttp processes untrusted input.

What to do: Upgrade aiohttp to 3.14.4 or later. Grep dependency manifests for aiohttp and check running versions against the patched release.</description>
    </item>
    <item>
      <title>NLTK dot2img enables local code execution via PATH manipulation</title>
      <link>https://radar.trulysovereign.com/items/a631b2fa-80eb-4fa3-b831-7833c05b3ee6</link>
      <guid isPermaLink="false">a631b2fa-80eb-4fa3-b831-7833c05b3ee6</guid>
      <pubDate>Mon, 16 Nov 2026 22:02:57 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>CVE-2026-128134 published 16 November 2026. NLTK's dot2img function runs Graphviz 'dot' without the trusted-exec chokepoint, allowing local code execution when an attacker controls a writable PATH element. First patched version: 3.10.4.

Why it matters: An attacker with write access to any directory in PATH can place a malicious 'dot' executable that NLTK will run with the application's privileges when dot2img is called. This bypasses the intended security boundary for external tool invocation.

What to do: Upgrade nltk to 3.10.4 or later. If you cannot upgrade immediately, audit PATH for writable directories and remove write permissions for untrusted users.</description>
    </item>
    <item>
      <title>aiohttp WebSocket receive queue limits bypassed by small messages</title>
      <link>https://radar.trulysovereign.com/items/6ee38546-5eb5-4f44-9d98-70cc88e7c05f</link>
      <guid isPermaLink="false">6ee38546-5eb5-4f44-9d98-70cc88e7c05f</guid>
      <pubDate>Mon, 16 Nov 2026 22:02:49 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>CVE-2026-128132 published 16 November 2026 as GHSA-5rmc-48h2-hvcm, rated high severity. Small or compressed WebSocket messages bypass receive queue limits in aiohttp. First patched version is 3.14.4.

Why it matters: An attacker can exhaust server resources by sending WebSocket messages that evade queue limits, causing denial of service. Applications using aiohttp WebSocket handling are exposed to resource exhaustion attacks.

What to do: Upgrade aiohttp to 3.14.4 or later. Grep for 'aiohttp' in requirements files and check deployed versions against the CVE scope.</description>
    </item>
    <item>
      <title>aiohttp WebSocket integer overflow bypasses max_msg_size</title>
      <link>https://radar.trulysovereign.com/items/63dec2da-4d8f-45bc-a8cc-24ba6bac1984</link>
      <guid isPermaLink="false">63dec2da-4d8f-45bc-a8cc-24ba6bac1984</guid>
      <pubDate>Mon, 16 Nov 2026 22:02:41 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>CVE-2026-128128 published 16 November 2026 for aiohttp, severity high. An integer overflow in WebSocket size validation allows messages to bypass max_msg_size limits. Patched in version 3.14.4.

Why it matters: Services using aiohttp WebSockets can receive messages larger than configured limits, potentially causing memory exhaustion or denial of service. The bypass is in protocol-level validation, so application-layer size checks do not prevent it.

What to do: Update aiohttp to 3.14.4 or later. If you run WebSocket endpoints with aiohttp, prioritize this in the current patch cycle.</description>
    </item>
    <item>
      <title>aiohttp 3.14.4 patches request replay and buffer growth vulnerability</title>
      <link>https://radar.trulysovereign.com/items/039ddc48-d9bc-430f-b22d-68eb94f840a9</link>
      <guid isPermaLink="false">039ddc48-d9bc-430f-b22d-68eb94f840a9</guid>
      <pubDate>Mon, 16 Nov 2026 22:02:32 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>GitHub published CVE-2026-128130 on 16 November 2026, a high-severity vulnerability in aiohttp's pure-Python parser that allows request replay and buffer growth behind a declined upgrade. First patched version is 3.14.4.

Why it matters: Request replay can bypass authentication or rate limiting by re-executing requests the server already declined. Unbounded buffer growth consumes memory until the process fails or the host runs out of resources.

What to do: Check your dependency tree for aiohttp versions below 3.14.4. If present, update to 3.14.4 or later in this cycle.</description>
    </item>
    <item>
      <title>[CORRECTED] dnspython CVE-2026-128089 causes excessive memory and CPU use</title>
      <link>https://radar.trulysovereign.com/items/ce2fd1aa-e455-44fb-8cec-215077e7c30a</link>
      <guid isPermaLink="false">ce2fd1aa-e455-44fb-8cec-215077e7c30a</guid>
      <pubDate>Sun, 15 Nov 2026 06:36:05 GMT</pubDate>
      <category>patch_now</category>
      <category>corrected</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>[CORRECTED] GitHub published GHSA-vvf4-9x63-8xvv on 13 November 2026, rating CVE-2026-128089 in dnspython as high severity. The vulnerability is in zone-file parsing: the `from_text()` parser does not limit a WKS record service number to 0–65535, so a maliciously crafted zone file can cause excessive memory and CPU consumption. Versions earlier than 2.9.2 are affected. First patched version is 2.9.2.

Why it matters: Applications are affected only when they parse zone-file text whose record type and rdata are attacker-controlled. Using dnspython only for DNS resolution, without parsing attacker-controlled zone-file text, does not match the advisory's stated impact. A high severity rating does not mean every deployment that includes the package is exposed.

What to do: If your code parses zone-file format with dnspython (including `dns.rdata.from_text`) where an attacker can control the record type and rdata, upgrade to version 2.9.2 or later. If you only use dnspython as a DNS resolver and do not parse untrusted zone-file text, this advisory does not describe a demonstrated exposure, though upgrading remains ordinary hygiene.

Original text (as first published, superseded):

WHAT CHANGED: GitHub published GHSA-vvf4-9x63-8xvv on 13 November 2026, rating CVE-2026-128089 in dnspython as high severity. The vulnerability causes excessive memory and CPU consumption. First patched version is 2.9.2.

WHY IT MATTERS: Services using dnspython for DNS resolution can experience availability degradation or denial of service through resource exhaustion. The high severity rating indicates exploitability affects production workloads.

WHAT TO DO: Upgrade dnspython to version 2.9.2 or later in services where it is a runtime dependency.</description>
    </item>
    <item>
      <title>[CORRECTED] PyJWT 2.13.0 accepts JWK public keys as HMAC secrets</title>
      <link>https://radar.trulysovereign.com/items/50c172c6-74a0-4090-a626-6f6df1236e26</link>
      <guid isPermaLink="false">50c172c6-74a0-4090-a626-6f6df1236e26</guid>
      <pubDate>Wed, 30 Sep 2026 21:59:39 GMT</pubDate>
      <category>patch_now</category>
      <category>corrected</category>
      <source url="https://api.github.com/advisories?ecosystem=pip&amp;severity=high&amp;per_page=100">GitHub advisories — pip</source>
      <description>[CORRECTED] CVE-2026-102273 (GHSA-w2cx-738m-mc7w) published 29 September 2026, rated high severity. PyJWT 2.13.0 accepts public JWK containers as HMAC secrets. Only version 2.13.0 is listed as vulnerable. Patched in 2.14.0.

Why it matters: An attacker who knows the public key can forge HS256/HS384/HS512 tokens, but only in applications that allow both HS* and asymmetric algorithms in one verification path and pass raw public JWK or JWKS JSON as the key. Applications that keep symmetric and asymmetric verification separate are not affected.

What to do: Check your dependency trees for PyJWT 2.13.0. If found, update to 2.14.0 this cycle. If any verification path accepts both HS* and asymmetric algorithms and passes JWK or JWKS data as the key, review those call sites first.

Original text (as first published, superseded):

HEADLINE: PyJWT accepts JWK public keys as HMAC secrets

WHAT CHANGED: CVE-2026-102273 published 29 September 2026. PyJWT before 2.14.0 accepts public JWK containers as HMAC secrets, rated high severity. Patched in 2.14.0.

WHY IT MATTERS: An attacker who controls the JWK input can forge tokens by supplying a public key where the application expects an HMAC secret, bypassing signature verification entirely. Any JWT validation using HMAC with externally-supplied keys is compromised.

WHAT TO DO: Grep your dependency trees for PyJWT &lt;2.14.0. If found, update to 2.14.0 this cycle. If you pass JWK data into JWT verification, audit those call sites for untrusted input before deploying the patch.</description>
    </item>
  </channel>
</rss>
