CVE-2026-133630: flowintel · Insufficiently Protected Credentials
Affects flowintelSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 4.1.0 when convenient.
Data as of 20 Nov 2026, 09:35 UTC
Thin evidence
One scorer or none| CNA (CIRCL) | CVSS 4.0 | 5.9 |
|---|
- Patch
- Available – fixed in 4.1.0
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| flowintelflowintel | Affected
| Fixed in
|
GitHubflowintelpkg:github/flowintelOther threats | Affected
| Fixed in
|
CPE configurations (1)
cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade flowintel to version 4.1.0 or later, where this issue is fixed. The fix removes the persistence of the job authentication token in the Git configuration file within the Docker build context, preventing token leakage via build cache layers.
Description
CVE-2026-133630 is a vulnerability in flowintel versions prior to 4.1.0 where the GitHub Actions checkout action used in the Docker build workflow persisted the job authentication token in the repository's Git configuration file. This file was included in the Docker build context and could be retained in exported build cache layers, potentially exposing the token. An attacker with access to the CI/CD build cache or environment could extract this token and gain unauthorized read access to the private source repository.