The flowintel Docker build workflow used the GitHub Actions checkout action with default credential persistence, causing the job authentication token to be written into the repository's Git configuration file
Source GCVE Database
Not known to be exploited · CVSS 5.9 Medium : upgrade to 4.1.0 when convenient.
Data as of 20 Nov 2026, 14:09 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
|
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 and later. Users should upgrade to version 4.1.0 or above to prevent token leakage. Until then, review and modify the Docker build workflow to avoid persisting credentials in the Git configuration file and ensure build cache layers do not retain sensitive tokens.
Description
The flowintel Docker build workflow used the GitHub Actions checkout action with default credential persistence, causing the job authentication token to be written into 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 build environment could extract this token and gain unauthorized read access to the private source repository. This vulnerability affects flowintel versions prior to 4.1.0.