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 became part of the Docker build context and could be retained in exported build cache layers, even though Git metadata was stripped from the final runtime image.

An attacker with access to the CI/CD build cache or build environment could extract the persisted token and use it to gain unauthorized access to the private source repository.

Impact:
- Exposure of a valid authentication token to the private repository
- Potential unauthorized read access to source code and repository metadata

Affected versions: flowintel < 4.1.0
Published: 2026-11-20
Score: 5.9 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

Vendor Solution

The checkout step is configured to not persist credentials into the workspace, and the full branch history is fetched during the authenticated checkout phase. This ensures the job token is never written to the Git configuration file that enters the Docker build context, eliminating the credential from build cache layers while preserving the ability to resolve release tags against the main branch.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 20 Nov 2026 09:30:00 +0000

Type Values Removed Values Added
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 became part of the Docker build context and could be retained in exported build cache layers, even though Git metadata was stripped from the final runtime image. An attacker with access to the CI/CD build cache or build environment could extract the persisted token and use it to gain unauthorized access to the private source repository. Impact: - Exposure of a valid authentication token to the private repository - Potential unauthorized read access to source code and repository metadata Affected versions: flowintel < 4.1.0
Title flowintel CI/CD Workflow Exposes Checkout Credentials in Docker Build Cache
First Time appeared Flowintel
Flowintel flowintel
Weaknesses CWE-200
CWE-522
CPEs cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*
Vendors & Products Flowintel
Flowintel flowintel
References
Metrics cvssV4_0

{'score': 5.9, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N'}


Subscriptions

Flowintel Flowintel
cve-icon MITRE

Status: PUBLISHED

Assigner: CIRCL

Published:

Updated: 2026-11-20T09:09:40.890Z

Reserved: 2026-11-20T09:09:38.574Z

Link: CVE-2026-133630

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-20T10:17:10.827

Modified: 2026-11-20T10:17:10.827

Link: CVE-2026-133630

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses