Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The trillium-client crate, versions before 0.5.4, does not check outbound header names and values for illegal bytes. An attacker who can control header content and inject CRLF sequences could split requests or responses, potentially exfiltrating data from other requests or enabling SSRF. Upgrade to trillium-client 0.5.4 or later, which rejects invalid headers before any network access. Until then, validate or sanitize untrusted input used in header names and values, rejecting carriage return, newline, and null characters.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.8 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0063, the 50th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:24 UTC First seen by agentprime
- 31 Oct 2026, 14:24 UTC Confirmed by OSV