Skip to main content
VulnerabilityPublished

CVE-2026-133627: its case history (audit log) subsystem · Flowintel Contains a Log Injection Vulnerability

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-133627· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.1.0 when convenient.

Data as of 20 Nov 2026, 10:34 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (CIRCL)CVSS 4.05.3
Patch
Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade flowintel to 4.1.0.

Affected software

ProductAffectedFixed in
flowintelflowintelAffected
  • <4.1.0
Fixed in
  • 4.1.0
GitHubflowintelpkg:github/flowintelOther threatsAffected
  • <4.1.0
Fixed in
  • 4.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in flowintel version 4.1.0. Users should upgrade to version 4.1.0 or later to remediate this vulnerability. Until then, restrict case-management access to trusted users only, as exploitation requires authenticated access with case history modification rights.

Description

flowintel versions prior to 4.1.0 contain a log injection vulnerability in the case history (audit log) subsystem. Authenticated users with case-management access can inject line separator characters into user-controlled fields, causing the audit log to record forged additional entries attributed to arbitrary users. This compromises the integrity of the audit trail without requiring privilege escalation or authentication bypass.

References

Community reviews

Loading reviews…