CVE-2026-81827
Received Received - Intake

Flowintel Login Email Validation Bypass Leads to Log Injection

Vulnerability report for CVE-2026-81827, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-27

Last updated on: 2026-08-27

Assigner: CIRCL

Description

Affected versions of Flowintel incorrectly attempted to validate login email addresses by calling Email(email). That does not perform WTForms field validation; it merely constructs a validator object. Consequently, malformed attacker-controlled email input could continue through the login process and be written to security-relevant logs. The vulnerable code inserted the supplied email into both a warning log and the custom audit logger. Since CR/LF characters were not escaped, an unauthenticated attacker could potentially inject additional physical log lines or forge misleading log entries. The patch corrects the validation call to Email()(form, form.email), changes the standard logging call to parameterized logging, and introduces _sanitize_log_fragment() so carriage returns and line feeds are encoded instead of creating new records. Version impacted >=3.3.0

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-27
Last Modified
2026-08-27
Generated
2026-08-27
AI Q&A
2026-08-27
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
flowintel flowintel From 3.3.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-20 The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves incorrect email validation in Flowintel versions 3.3.0 and above. The code used Email(email) which only creates a validator object without performing proper validation. This allowed malformed attacker-controlled email input to bypass checks and be logged unsafely.

Detection Guidance

Check logs for unusual entries containing CR/LF characters or malformed email addresses. Look for log entries with injected line breaks or forged entries in security-relevant logs.

Impact Analysis

An unauthenticated attacker could inject CR/LF characters into email input to forge log entries or add fake log lines. This could mislead security monitoring, create false audit trails, or obscure real security events in logs.

Mitigation Strategies

Apply the patch that updates the email validation to use Email()(form, form.email) and implements parameterized logging. Ensure logs are sanitized to escape CR/LF characters using _sanitize_log_fragment().

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-81827. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart