Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') in trillium-http and trillium-client

Exploitation

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

CVSS

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

EPSS

• CVE-2024-23644: 0.63% estimated exploitation activity in the next 30 days; percentile 50.34 (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.

Summary Insufficient validation of outbound header values may lead to request splitting or response splitting attacks in scenarios where attackers have sufficient control over outbound headers. Details Outbound trilliumhttp::HeaderValue and trilliumhttp::HeaderName can be constructed infallibly and were not checked for illegal bytes when sending requests from the client or responses from the server. Thus, if an attacker has sufficient control over header values (or names) in a request or response that they could inject \r\n sequences, they could get the client and server out of sync, and then pivot to gain control over other parts of requests or responses. (i.e. exfiltrating data from other requests, SSRF, etc.) Patches trillium-http = 0.3.12: If a header name is invalid in server response headers, the specific header and any associated values are omitted from network transmission. If a header value is invalid in server response headers, the individual header value is omitted from…

Published by the source

24 Jan 2024, 20:20 UTC

Last modified by the source

2 Feb 2024, 18:42 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9f9p-cp3c-72jf

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

# Patch Next advisory brief: CVE-2024-23644

Advisory: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') in trillium-http and trillium-client
IDs: CVE-2024-23644, GHSA-9f9p-cp3c-72jf
Record: https://patchnext.com/advisories/cve-2024-23644 (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: trillium-client 0.5.4; trillium-http 0.3.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io trillium-client: affected < 0.5.4; fixed in 0.5.4
- crates.io trillium-http: affected < 0.3.12; fixed in 0.3.12

## Suggested inspection (read-only)
- crates.io trillium-client: check the installed version with your package manager.
- crates.io trillium-http: check the installed version with your package manager.

## 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 trillium-client, trillium-http.
- 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://github.com/advisories/GHSA-9f9p-cp3c-72jf (GitHub-reviewed advisory GHSA-9f9p-cp3c-72jf lists affected ranges: crates.io trillium-http >=0 =0 <0.5.4)

Commands are suggestions: review each one before running it.