Script execution via CRLF header injection
Published Aug 24, 2026 · Updated Aug 24, 2026
CRLF injection in TIM Solutions GmbH TIM Flow before 26.0.6 allows remote attackers to inject HTTP headers through the rt URL parameter. Set-Cookie response generation copies unsanitized carriage return and line feed sequences from rt, enabling response splitting and attacker-controlled body content. Exploitation requires an authenticated user to open a crafted request, after which injected JavaScript can steal session tokens or modify account credentials.
Summary
What happened
CRLF injection in TIM Solutions GmbH TIM Flow before 26.0.6 allows remote attackers to inject HTTP headers through the rt URL parameter. Set-Cookie response generation copies unsanitized carriage return and line feed sequences from rt, enabling response splitting and attacker-controlled body content. Exploitation requires an authenticated user to open a crafted request, after which injected JavaScript can steal session tokens or modify account credentials.
The record
- CVE
- CVE-2026-39915
- Published
- Aug 24, 2026
- Updated
- Aug 24, 2026
- Vendor
- TIM Solutions GmbH
- Product
- TIM Flow
- Classifications
- CWE-113, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2026CVE publishedPublication date reported by the CVE source.
- Aug 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <26.0.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo