<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 18:10:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-33752 — Redirect-based SSRF leading to internal network access in curl_cffi (with TLS impersonation bypass)</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-33752</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; lexiforest curl_cffi&lt;/p&gt;
&lt;p&gt;curl_cffi is the a Python binding for curl. Prior to 0.15.0, curl_cffi does not restrict requests to internal IP ranges, and follows redirects automatically via the underlying libcurl. Because of this, an attacker-controlled URL can redirect requests to internal services such as cloud metadata endpoints. In addition, curl_cffi’s TLS impersonation feature can make these requests appear as legitimate browser traffic, which may bypass certain network controls. This vulnerability is fixed in 0.15.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; lexiforest curl_cffi&lt;/p&gt;
&lt;p&gt;curl_cffi is the a Python binding for curl. Prior to 0.15.0, curl_cffi does not restrict requests to internal IP ranges, and follows redirects automatically via the underlying libcurl. Because of this, an attacker-controlled URL can redirect requests to internal services such as cloud metadata endpoints. In addition, curl_cffi’s TLS impersonation feature can make these requests appear as legitimate browser traffic, which may bypass certain network controls. This vulnerability is fixed in 0.15.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-33752</guid>
    </item>
    <item>
      <title>GHSA-qw2m-4pqf-rmpp — curl_cffi: Redirect-based SSRF leads to internal network access in curl_cffi (with TLS impersonation bypass)</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-qw2m-4pqf-rmpp</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: curl_cffi&lt;/p&gt;
&lt;p&gt;### Summary
curl_cffi does not restrict requests to internal IP ranges, and follows redirects automatically via the underlying libcurl.&lt;/p&gt;
&lt;p&gt;Because of this, an attacker-controlled URL can redirect requests to internal services such as cloud metadata endpoints. In addition, curl_cffi’s TLS impersonation feature can make these requests appear as legitimate browser traffic, which may bypass certain network controls.&lt;/p&gt;
&lt;p&gt;### Details
The issue comes from how curl_cffi handles outbound requests
- User-supplied URLs are passed directly to libcurl without checking whether they resolve to internal IP ranges (e.g., 127.0.0.1, 169.254.0.0/16).
- Redirects are automatically followed (CURLOPT_FOLLOWLOCATION = 1) inside libcurl.
- There is no validation of redirect destinations at the Python layer.&lt;/p&gt;
&lt;p&gt;This means that even if an application only allows requests to external URLs, an attacker can
- Provide a URL pointing to an attacker-controlled server
- Return a redirect response pointing to an internal service
- Have curl_cffi follow that redirect automatically&lt;/p&gt;
&lt;p&gt;As a result, internal endpoints (such as cloud instance metadata APIs) can be accessed.&lt;/p&gt;
&lt;p&gt;Additionally, curl_cffi supports TLS fingerprint impersonation (e.g., impersonate=&amp;#34;chrome&amp;#34;). In environments where outbound requests are filtered based on TLS fingerprinting, this can make such requests harder to detect or block&lt;/p&gt;
&lt;p&gt;This behavior is similar to previously reported redirect-based SSRF issues such as CVE-2025-68616, where redirects allowed…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: curl_cffi&lt;/p&gt;
&lt;p&gt;### Summary
curl_cffi does not restrict requests to internal IP ranges, and follows redirects automatically via the underlying libcurl.&lt;/p&gt;
&lt;p&gt;Because of this, an attacker-controlled URL can redirect requests to internal services such as cloud metadata endpoints. In addition, curl_cffi’s TLS impersonation feature can make these requests appear as legitimate browser traffic, which may bypass certain network controls.&lt;/p&gt;
&lt;p&gt;### Details
The issue comes from how curl_cffi handles outbound requests
- User-supplied URLs are passed directly to libcurl without checking whether they resolve to internal IP ranges (e.g., 127.0.0.1, 169.254.0.0/16).
- Redirects are automatically followed (CURLOPT_FOLLOWLOCATION = 1) inside libcurl.
- There is no validation of redirect destinations at the Python layer.&lt;/p&gt;
&lt;p&gt;This means that even if an application only allows requests to external URLs, an attacker can
- Provide a URL pointing to an attacker-controlled server
- Return a redirect response pointing to an internal service
- Have curl_cffi follow that redirect automatically&lt;/p&gt;
&lt;p&gt;As a result, internal endpoints (such as cloud instance metadata APIs) can be accessed.&lt;/p&gt;
&lt;p&gt;Additionally, curl_cffi supports TLS fingerprint impersonation (e.g., impersonate=&amp;#34;chrome&amp;#34;). In environments where outbound requests are filtered based on TLS fingerprinting, this can make such requests harder to detect or block&lt;/p&gt;
&lt;p&gt;This behavior is similar to previously reported redirect-based SSRF issues such as CVE-2025-68616, where redirects allowed…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-qw2m-4pqf-rmpp</guid>
    </item>
    <item>
      <title>PYSEC-2026-2431 — curl_cffi: Redirect-based SSRF leads to internal network access in curl_cffi (with TLS impersonation bypass)</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-2431</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: curl-cffi&lt;/p&gt;
&lt;p&gt;### Summary
curl_cffi does not restrict requests to internal IP ranges, and follows redirects automatically via the underlying libcurl.&lt;/p&gt;
&lt;p&gt;Because of this, an attacker-controlled URL can redirect requests to internal services such as cloud metadata endpoints. In addition, curl_cffi’s TLS impersonation feature can make these requests appear as legitimate browser traffic, which may bypass certain network controls.&lt;/p&gt;
&lt;p&gt;### Details
The issue comes from how curl_cffi handles outbound requests
- User-supplied URLs are passed directly to libcurl without checking whether they resolve to internal IP ranges (e.g., 127.0.0.1, 169.254.0.0/16).
- Redirects are automatically followed (CURLOPT_FOLLOWLOCATION = 1) inside libcurl.
- There is no validation of redirect destinations at the Python layer.&lt;/p&gt;
&lt;p&gt;This means that even if an application only allows requests to external URLs, an attacker can
- Provide a URL pointing to an attacker-controlled server
- Return a redirect response pointing to an internal service
- Have curl_cffi follow that redirect automatically&lt;/p&gt;
&lt;p&gt;As a result, internal endpoints (such as cloud instance metadata APIs) can be accessed.&lt;/p&gt;
&lt;p&gt;Additionally, curl_cffi supports TLS fingerprint impersonation (e.g., impersonate=&amp;#34;chrome&amp;#34;). In environments where outbound requests are filtered based on TLS fingerprinting, this can make such requests harder to detect or block&lt;/p&gt;
&lt;p&gt;This behavior is similar to previously reported redirect-based SSRF issues such as CVE-2025-68616, where redirects allowed…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: curl-cffi&lt;/p&gt;
&lt;p&gt;### Summary
curl_cffi does not restrict requests to internal IP ranges, and follows redirects automatically via the underlying libcurl.&lt;/p&gt;
&lt;p&gt;Because of this, an attacker-controlled URL can redirect requests to internal services such as cloud metadata endpoints. In addition, curl_cffi’s TLS impersonation feature can make these requests appear as legitimate browser traffic, which may bypass certain network controls.&lt;/p&gt;
&lt;p&gt;### Details
The issue comes from how curl_cffi handles outbound requests
- User-supplied URLs are passed directly to libcurl without checking whether they resolve to internal IP ranges (e.g., 127.0.0.1, 169.254.0.0/16).
- Redirects are automatically followed (CURLOPT_FOLLOWLOCATION = 1) inside libcurl.
- There is no validation of redirect destinations at the Python layer.&lt;/p&gt;
&lt;p&gt;This means that even if an application only allows requests to external URLs, an attacker can
- Provide a URL pointing to an attacker-controlled server
- Return a redirect response pointing to an internal service
- Have curl_cffi follow that redirect automatically&lt;/p&gt;
&lt;p&gt;As a result, internal endpoints (such as cloud instance metadata APIs) can be accessed.&lt;/p&gt;
&lt;p&gt;Additionally, curl_cffi supports TLS fingerprint impersonation (e.g., impersonate=&amp;#34;chrome&amp;#34;). In environments where outbound requests are filtered based on TLS fingerprinting, this can make such requests harder to detect or block&lt;/p&gt;
&lt;p&gt;This behavior is similar to previously reported redirect-based SSRF issues such as CVE-2025-68616, where redirects allowed…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-2431</guid>
    </item>
  </channel>
</rss>
