Skip to main content

CVE-2026-133630flowintel insufficiently protected credentials

Low priorityMedium5.9EPSS not scored yet

CVE-2026-133630 is a insufficiently protected credentials in flowintel, rated medium (5.9 on CVSS 4.0).

Why this priority: Medium severity, with no exploitation signal.

Published · Updated · NVD status: Received

What it is

Credentials are stored or sent in a way others can recover. The software reveals data to someone who should not see it.

How it is reached

An attacker can exploit it by someone who can already run code or sign in on the machine, with an administrator account, and nobody has to click anything.

What an attacker gains

The scored direct impact on the component itself is low. In practice, this kind of flaw lets an attacker sign in with credentials the vendor shipped or stored unprotected. The damage can spread past the vulnerable component into others.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade flowintel to 4.1.0 or later.
  2. Limit who can run code or sign in on the hosts that run it.

Description from NVD

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

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Credentials kept in code, configuration, images or firmware. The flaw sits between a stored secret and anyone who can read where it is kept.
  • Error responses, logs and debug endpoints. The flaw sits between internal data and whoever can read the response or log.
  • APIs that over-share. The flaw sits between internal data and whoever can read the response or log.

Trust boundaries in play

  • Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
  • Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
  • Between a stored secret and anyone who can read where it is kept. An attacker who crosses it can sign in with credentials the vendor shipped or stored unprotected.
  • Between internal data and whoever can read the response or log. An attacker who crosses it can learn data or internals that help a follow-up attack.

Questions to answer about your own systems

  • Where does flowintel run in your systems, and at which version?
  • Which of those hosts also run code or users you do not fully trust?
  • What can it reach once compromised: which data stores, secrets and services?

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.