Skip to content
Web

CVE-2026-39915

8.5
High
EPSS 0.27%Patch availableAug 25, 2026

CRLF injection in TIM Flow rt parameter enables header injection and consequent XSS leading to session theft.

common questions

Is CVE-2026-39915 being exploited?

Not confirmed. CVE-2026-39915 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.

How severe is CVE-2026-39915?

CVE-2026-39915 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-39915?

Yes. A fix has been recorded for CVE-2026-39915. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-39915 affect?

CVE-2026-39915 affects TIM Flow versions prior to 26.0.6, TIM Flow web interface. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-39915?

Upgrade TIM Flow to 26.0.6+, sanitize rt input and apply WAF rule blocking CRLF sequences.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
TIM Flow versions prior to 26.0.6TIM Flow web interface
impact

Remote CRLF injection via rt param to inject Set-Cookie and response body, enabling authenticated-user XSS, session token theft and account takeover.

action required

Immediate action required

affected versions
TIM Solutions TIM Flow
  • affected< 26.0.6

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free