Gakido vulnerable to HTTP Header Injection (CRLF Injection)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS

• CVE-2026-24489: 0.40% estimated exploitation activity in the next 30 days; percentile 33.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. 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. Impact An attacker who can control header values passed to Gakido's Client.get(), Client.post(), or other request methods could: 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 Proof of Concept Affected Code The vulnerability existed in the header processing logic where user-supplied headers were not…

Published by the source

26 Jan 2026, 23:29 UTC

Last modified by the source

7 Jul 2026, 17:57 UTC

Source last checked

26 Oct 2026, 13:36 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-gcgx-chcp-hxp9

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-gcgx-chcp-hxp9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-24489

Advisory: Gakido vulnerable to HTTP Header Injection (CRLF Injection)
IDs: CVE-2026-24489, GHSA-gcgx-chcp-hxp9
Record: https://patchnext.com/advisories/cve-2026-24489 (revision 2, source checked 26 Oct 2026, 13:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gakido 0.1.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI gakido: affected < 0.1.1; fixed in 0.1.1

## Suggested inspection (read-only)
- `python -m pip show gakido`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gakido.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-gcgx-chcp-hxp9 (OSV record GHSA-gcgx-chcp-hxp9 lists affected ranges: PyPI gakido >=0 <0.1.1 (fixed))
- Verified: https://github.com/advisories/GHSA-gcgx-chcp-hxp9 (GitHub-reviewed advisory GHSA-gcgx-chcp-hxp9 lists affected ranges: PyPI gakido >=0 <0.1.1)

Commands are suggestions: review each one before running it.