<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T19:09:00.496696+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/cve-2026-25645</id>
    <title>CVE-2026-25645 — Requests has Insecure Temp File Reuse in its extract_zipped_paths() utility function</title>
    <updated>2026-10-06T19:09:00.504018+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> psf requests</p>
<p>Requests is a HTTP library. Prior to version 2.33.0, the `requests.utils.extract_zipped_paths()` utility function uses a predictable filename when extracting files from zip archives into the system temporary directory. If the target file already exists, it is reused without validation. A local attacker with write access to the temp directory could pre-create a malicious file that would be loaded in place of the legitimate one. Standard usage of the Requests library is not affected by this vulnerability. Only applications that call `extract_zipped_paths()` directly are impacted. Starting in version 2.33.0, the library extracts files to a non-deterministic location. If developers are unable to upgrade, they can set `TMPDIR` in their environment to a directory with restricted write access.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-25645"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-752w-5fwx-jx9f</id>
    <title>GHSA-752w-5fwx-jx9f — PyJWT accepts unknown `crit` header extensions</title>
    <updated>2026-10-06T19:09:00.504085+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: PyJWT</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://cve.radiocsirt.org/vuln/ghsa-752w-5fwx-jx9f"/>
  </entry>
</feed>
