# CVE-2026-81827: Flowintel Login Email Validation Bypass Allows Log Injection via Crafted Email Input

> Unauthenticated attackers can inject log entries via crafted email input due to improper validation, potentially forging audit logs.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-3hq8-r684-4qwf

## What is CVE-2026-81827?

CVE-2026-81827 is a medium-severity vulnerability in flowintel, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-81827?


## How do I fix CVE-2026-81827?

No fix has been published for CVE-2026-81827 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-81827 being exploited?

There is no known exploitation of CVE-2026-81827 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81827 and fix it if it is affected.

What it is: CVE-2026-81827 is a medium-severity vulnerability in flowintel, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-81827 in the wild and no public exploit code.

Affected product: flowintel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-81827/ (Markdown: https://insights.sbomify.com/CVE-2026-81827/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-81827
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-81827
- OSV: https://osv.dev/vulnerability/CVE-2026-81827

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-81827/
Summaries are generated and may contain mistakes; the official description above is the record.