CVE-2026-81827

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
6.9
EG Score
6.9(medium)
EG Risk
36(Track)
EG Risk 36/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 computed
Severity69% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Aug 27, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit 660b4cc40505 (flowintel/flowintel)

Fix landed in flowintel/flowintel commit 660b4cc40505 — awaiting tagged release

https://github.com/flowintel/flowintel/commit/660b4cc405055a794f157d3e4612520f12fe65bf

Vendor Advisories for CVE-2026-81827(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 9× in last 7d / 9× 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.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 17:52 UTCEG score recompute
  3. 2026-08-29 17:52 UTCGHSA enrichment
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-28 15:43 UTCGHSA enrichment
  6. 2026-08-27 20:28 UTCGHSA enrichment
  7. 2026-08-27 17:27 UTCEG score recompute
  8. 2026-08-27 16:48 UTCEG score recompute
  9. 2026-08-27 16:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81827?
CVE-2026-81827 is a medium vulnerability published on August 27, 2026. 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…
When was CVE-2026-81827 disclosed?
CVE-2026-81827 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81827 actively exploited?
CVE-2026-81827 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.3% of all scored CVEs.
What is the CVSS score of CVE-2026-81827?
CVE-2026-81827 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-81827?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81827, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-81827

Explore →

Is Your Infrastructure Affected by CVE-2026-81827?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.