TIM Flow before 26.0.6 contains a CRLF injection vulnerability that allows remote attackers to inject arbitrary HTTP headers and response body content by embedding unsanitized carriage return and line feed sequences in the rt URL parameter, which is reflected into Set-Cookie response headers. Attackers can craft malicious requests to induce authenticated users to execute arbitrary JavaScript in their browser context, enabling session token theft and account credential modification.
CVE-2026-39915
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. a secondary CVSS source baseline 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(high)
- EG Risk
- 41(Track)EG Risk 41/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity81% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
August 24, 2026
Last Modified
August 24, 2026
Advisory Details (2)
Auto-updated Aug 24, 2026TIM Flow < 26.0.6 CRLF Injection via rt Parameter and access_token Cookie | Advisories | VulnCheck
https://www.vulncheck.com/advisories/tim-flow-crlf-injection-via-rt-parameter-and-access-token-cookieVendor Advisories for CVE-2026-39915(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 17:50 UTCEG score recompute
- 2026-08-25 17:50 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 05:34 UTCGHSA enrichment
- 2026-08-24 17:19 UTCGHSA enrichment
- 2026-08-24 16:25 UTCEG score recompute
- 2026-08-24 16:25 UTCGHSA enrichment
- 2026-08-24 15:32 UTCEG score recompute
- 2026-08-24 15:32 UTCGHSA enrichment
- 2026-08-24 15:23 UTCEG score recompute
- 2026-08-24 14:21 UTCEG score recompute
- 2026-08-24 14:21 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-39915?
When was CVE-2026-39915 disclosed?
Is CVE-2026-39915 actively exploited?
What is the CVSS score of CVE-2026-39915?
How do I remediate CVE-2026-39915?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-39915
Is Your Infrastructure Affected by CVE-2026-39915?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.