CVE-2026-133630: flowintel CI/CD Workflow Exposes Checkout Credentials in Docker Build Cache

Published Nov 20, 2026
·
Updated

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

Affected Software

1 affected component
Flowintel<4.1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Disable credential persistence so the job authentication token is not written to the repository's Git configuration file in the Docker build context.

    GitHub Actions checkout step credential persistence = disabled

Event History

Nov 20, 2026
CVE Published
via MITRE·09:09 AM
Data Sourced
via MITRE·09:09 AM
RemedyDescriptionWeakness
Data Sourced
via OSV·09:09 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Organizations using affected flowintel versions earlier than 4.1.0 with the vulnerable Docker build workflow are exposed if an attacker can access the CI/CD build cache or build environment. The primary risk is unauthorized read access to the private source repository and its metadata.

2

What access does an attacker need to exploit it?

An attacker needs access to exported Docker build cache layers or the CI/CD build environment. They could extract the GitHub Actions checkout token persisted in the repository Git configuration included in the Docker build context.

3

Is the final runtime image affected?

Git metadata was stripped from the final runtime image. However, the token could remain recoverable from exported Docker build cache layers because the Git configuration entered the Docker build context.

4

How can teams determine whether they may be affected?

Check whether flowintel is below version 4.1.0 and whether its CI/CD Docker build workflow uses GitHub Actions checkout with default credential persistence. Also review who can access build environments and exported build caches that may contain historical layers.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203