<?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://cve.radiocsirt.org</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, 06 Oct 2026 20:33:53 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-266650</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-266650</link>
      <description>EUVD-2026-266650</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-266650</guid>
    </item>
    <item>
      <title>fkie_cve-2026-24489</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-24489</link>
      <description>&lt;p&gt;Gakido is a Python HTTP client focused on browser impersonation and anti-bot evasion. A vulnerability was discovered in Gakido prior to version 0.1.1 that allowed HTTP header injection through CRLF (Carriage Return Line Feed) sequences in user-supplied header values and names. When making HTTP requests with user-controlled header values containing `\r\n` (CRLF), `\n` (LF), or `\x00` (null byte) characters, an attacker could inject arbitrary HTTP headers into the request. The fix in version 0.1.1 adds a `_sanitize_header()` function that strips `\r`, `\n`, and `\x00` characters from both header names and values before they are included in HTTP requests.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Gakido is a Python HTTP client focused on browser impersonation and anti-bot evasion. A vulnerability was discovered in Gakido prior to version 0.1.1 that allowed HTTP header injection through CRLF (Carriage Return Line Feed) sequences in user-supplied header values and names. When making HTTP requests with user-controlled header values containing `\r\n` (CRLF), `\n` (LF), or `\x00` (null byte) characters, an attacker could inject arbitrary HTTP headers into the request. The fix in version 0.1.1 adds a `_sanitize_header()` function that strips `\r`, `\n`, and `\x00` characters from both header names and values before they are included in HTTP requests.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-24489</guid>
    </item>
    <item>
      <title>GHSA-gcgx-chcp-hxp9 — Gakido vulnerable to HTTP Header Injection (CRLF Injection)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-gcgx-chcp-hxp9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: gakido&lt;/p&gt;
&lt;p&gt;A vulnerability was discovered in Gakido that allowed HTTP Header Injection through CRLF (Carriage Return Line Feed) sequences in user-supplied header values and names.&lt;/p&gt;
&lt;p&gt;When making HTTP requests with user-controlled header values containing `\r\n` (CRLF), `\n` (LF), or `\x00` (null byte) characters, an attacker could inject arbitrary HTTP headers into the request.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can control header values passed to Gakido&amp;#39;s `Client.get()`, `Client.post()`, or other request methods could:&lt;/p&gt;
&lt;p&gt;1. **Inject arbitrary HTTP headers** - Add malicious headers to requests
2. **HTTP Response Splitting** - Potentially manipulate responses in certain proxy configurations
3. **Cache Poisoning** - Inject headers that could poison intermediate caches
4. **Session Fixation** - Inject session-related headers
5. **Bypass Security Controls** - Inject headers that bypass server-side security checks&lt;/p&gt;
&lt;p&gt;## Proof of Concept&lt;/p&gt;
&lt;p&gt;```python
from gakido import Client&lt;/p&gt;
&lt;p&gt;# Before fix: X-Injected header would be sent as a separate header
c = Client(impersonate=&amp;#34;chrome_120&amp;#34;)
r = c.get(&amp;#34;https://httpbin.org/headers&amp;#34;, headers={
    &amp;#34;User-Agent&amp;#34;: &amp;#34;test\r\nX-Injected: pwned&amp;#34;
})&lt;/p&gt;
&lt;p&gt;# The server would receive:
# User-Agent: test
# X-Injected: pwned
```&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;The vulnerability existed in the header processing logic where user-supplied headers were not sanitized before being sent in HTTP requests.&lt;/p&gt;
&lt;p&gt;**File:** `gakido/headers.py`  
**Function:** `canonicalize_headers()`&lt;/p&gt;
&lt;p&gt;## Fix&lt;/p&gt;
&lt;p&gt;The fix adds a `_sanit…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: gakido&lt;/p&gt;
&lt;p&gt;A vulnerability was discovered in Gakido that allowed HTTP Header Injection through CRLF (Carriage Return Line Feed) sequences in user-supplied header values and names.&lt;/p&gt;
&lt;p&gt;When making HTTP requests with user-controlled header values containing `\r\n` (CRLF), `\n` (LF), or `\x00` (null byte) characters, an attacker could inject arbitrary HTTP headers into the request.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can control header values passed to Gakido&amp;#39;s `Client.get()`, `Client.post()`, or other request methods could:&lt;/p&gt;
&lt;p&gt;1. **Inject arbitrary HTTP headers** - Add malicious headers to requests
2. **HTTP Response Splitting** - Potentially manipulate responses in certain proxy configurations
3. **Cache Poisoning** - Inject headers that could poison intermediate caches
4. **Session Fixation** - Inject session-related headers
5. **Bypass Security Controls** - Inject headers that bypass server-side security checks&lt;/p&gt;
&lt;p&gt;## Proof of Concept&lt;/p&gt;
&lt;p&gt;```python
from gakido import Client&lt;/p&gt;
&lt;p&gt;# Before fix: X-Injected header would be sent as a separate header
c = Client(impersonate=&amp;#34;chrome_120&amp;#34;)
r = c.get(&amp;#34;https://httpbin.org/headers&amp;#34;, headers={
    &amp;#34;User-Agent&amp;#34;: &amp;#34;test\r\nX-Injected: pwned&amp;#34;
})&lt;/p&gt;
&lt;p&gt;# The server would receive:
# User-Agent: test
# X-Injected: pwned
```&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;The vulnerability existed in the header processing logic where user-supplied headers were not sanitized before being sent in HTTP requests.&lt;/p&gt;
&lt;p&gt;**File:** `gakido/headers.py`  
**Function:** `canonicalize_headers()`&lt;/p&gt;
&lt;p&gt;## Fix&lt;/p&gt;
&lt;p&gt;The fix adds a `_sanit…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-gcgx-chcp-hxp9</guid>
    </item>
    <item>
      <title>PYSEC-2026-1400 — Gakido vulnerable to HTTP Header Injection (CRLF Injection)</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-1400</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: gakido&lt;/p&gt;
&lt;p&gt;A vulnerability was discovered in Gakido that allowed HTTP Header Injection through CRLF (Carriage Return Line Feed) sequences in user-supplied header values and names.&lt;/p&gt;
&lt;p&gt;When making HTTP requests with user-controlled header values containing `\r\n` (CRLF), `\n` (LF), or `\x00` (null byte) characters, an attacker could inject arbitrary HTTP headers into the request.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can control header values passed to Gakido&amp;#39;s `Client.get()`, `Client.post()`, or other request methods could:&lt;/p&gt;
&lt;p&gt;1. **Inject arbitrary HTTP headers** - Add malicious headers to requests
2. **HTTP Response Splitting** - Potentially manipulate responses in certain proxy configurations
3. **Cache Poisoning** - Inject headers that could poison intermediate caches
4. **Session Fixation** - Inject session-related headers
5. **Bypass Security Controls** - Inject headers that bypass server-side security checks&lt;/p&gt;
&lt;p&gt;## Proof of Concept&lt;/p&gt;
&lt;p&gt;```python
from gakido import Client&lt;/p&gt;
&lt;p&gt;# Before fix: X-Injected header would be sent as a separate header
c = Client(impersonate=&amp;#34;chrome_120&amp;#34;)
r = c.get(&amp;#34;https://httpbin.org/headers&amp;#34;, headers={
    &amp;#34;User-Agent&amp;#34;: &amp;#34;test\r\nX-Injected: pwned&amp;#34;
})&lt;/p&gt;
&lt;p&gt;# The server would receive:
# User-Agent: test
# X-Injected: pwned
```&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;The vulnerability existed in the header processing logic where user-supplied headers were not sanitized before being sent in HTTP requests.&lt;/p&gt;
&lt;p&gt;**File:** `gakido/headers.py`  
**Function:** `canonicalize_headers()`&lt;/p&gt;
&lt;p&gt;## Fix&lt;/p&gt;
&lt;p&gt;The fix adds a `_sanit…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: gakido&lt;/p&gt;
&lt;p&gt;A vulnerability was discovered in Gakido that allowed HTTP Header Injection through CRLF (Carriage Return Line Feed) sequences in user-supplied header values and names.&lt;/p&gt;
&lt;p&gt;When making HTTP requests with user-controlled header values containing `\r\n` (CRLF), `\n` (LF), or `\x00` (null byte) characters, an attacker could inject arbitrary HTTP headers into the request.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can control header values passed to Gakido&amp;#39;s `Client.get()`, `Client.post()`, or other request methods could:&lt;/p&gt;
&lt;p&gt;1. **Inject arbitrary HTTP headers** - Add malicious headers to requests
2. **HTTP Response Splitting** - Potentially manipulate responses in certain proxy configurations
3. **Cache Poisoning** - Inject headers that could poison intermediate caches
4. **Session Fixation** - Inject session-related headers
5. **Bypass Security Controls** - Inject headers that bypass server-side security checks&lt;/p&gt;
&lt;p&gt;## Proof of Concept&lt;/p&gt;
&lt;p&gt;```python
from gakido import Client&lt;/p&gt;
&lt;p&gt;# Before fix: X-Injected header would be sent as a separate header
c = Client(impersonate=&amp;#34;chrome_120&amp;#34;)
r = c.get(&amp;#34;https://httpbin.org/headers&amp;#34;, headers={
    &amp;#34;User-Agent&amp;#34;: &amp;#34;test\r\nX-Injected: pwned&amp;#34;
})&lt;/p&gt;
&lt;p&gt;# The server would receive:
# User-Agent: test
# X-Injected: pwned
```&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;The vulnerability existed in the header processing logic where user-supplied headers were not sanitized before being sent in HTTP requests.&lt;/p&gt;
&lt;p&gt;**File:** `gakido/headers.py`  
**Function:** `canonicalize_headers()`&lt;/p&gt;
&lt;p&gt;## Fix&lt;/p&gt;
&lt;p&gt;The fix adds a `_sanit…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-1400</guid>
    </item>
  </channel>
</rss>
