# CVE-2026-124850: SQL Injection in Database Migration via Stored Connector Identifiers in flowintel


- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-29rj-4jqp-xhr4

## What is CVE-2026-124850?

CVE-2026-124850 is a high-severity vulnerability in flowintel, published on 9 Nov 2026. 

### Official description

A SQL injection vulnerability exists in a database migration script in flowintel.

The migration process reads stored connector identifier values from the database and interpolates them directly into SQL statements without parameterization. An attacker who has previously written a malicious identifier value into the affected tables can cause arbitrary SQL execution when the migration is subsequently run during an application upgrade.

- Requires prior write access to the database to plant a malicious identifier value
- Triggered automatically during a migration or upgrade operation
- Can result in unauthorized data disclosure, modification, or deletion

Affected versions: flowintel prior to 4.0.0

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-124850?


## How do I fix CVE-2026-124850?

No fix has been published for CVE-2026-124850 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-124850 being exploited?

There is no known exploitation of CVE-2026-124850 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124850 and fix it if it is affected.

What it is: CVE-2026-124850 is a high-severity vulnerability in flowintel, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124850 in the wild and no public exploit code.

Affected product: flowintel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-124850/ (Markdown: https://insights.sbomify.com/CVE-2026-124850/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-124850
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-124850
- OSV: https://osv.dev/vulnerability/CVE-2026-124850

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-124850/
Summaries are generated and may contain mistakes; the official description above is the record.