<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>PyJWT - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/pyjwt/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Sat, 08 Aug 2026 09:32:04 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/pyjwt/feed.xml" rel="self" type="application/rss+xml"/><item><title>PyJWT Improper Handling of Critical Header Extensions (CVE-2026-32597)</title><link>https://feed.craftedsignal.io/briefs/2026-08-pyjwt-crit-header-vulnerability/</link><pubDate>Sat, 08 Aug 2026 09:32:04 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-pyjwt-crit-header-vulnerability/</guid><description>The PyJWT library fails to reject unknown 'crit' header extensions as required by RFC 7515, creating a potential bypass vulnerability in JWT integrity and authentication checks.</description><content:encoded><![CDATA[<p>CVE-2026-32597 identifies a specification compliance vulnerability within the PyJWT library where the parser incorrectly handles the 'crit' (critical) header parameter defined in JSON Web Signature (JWS) specifications. According to RFC 7515 §4.1.11, a JWT validator must reject any JWS if it contains a 'crit' header parameter that includes extensions not understood by the application. Because PyJWT currently accepts these unknown extensions, an attacker may be able to craft malicious JWTs that include unsupported critical headers to bypass security validations, potentially leading to unauthorized access or identity spoofing depending on how the application processes the claims. This vulnerability impacts applications relying on PyJWT for critical authentication and authorization workflows.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation could allow an attacker to bypass authentication mechanisms or modify the behavior of the validation process by including unrecognized but critical headers. This could result in the acceptance of malformed or unauthorized tokens. The scope of impact is dependent on the specific implementation of the downstream application using the vulnerable PyJWT library version.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Identify applications and microservices using PyJWT versions vulnerable to CVE-2026-32597.</li>
<li>Update the PyJWT dependency to the latest patched version provided by the maintainer.</li>
<li>Review application logic that processes JWS tokens to ensure strict validation of header parameters where possible until patching is complete.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category></item></channel></rss>