# CVE-2026-39914: TIM Flow < 26.0.6 Unauthorized SQL Query Execution via Dashboard Export Endpoint

> Authenticated users can execute arbitrary SQL queries via a dashboard export endpoint, bypassing access controls to retrieve sensitive database contents.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-jv9g-4xc8-gqg7

## What is CVE-2026-39914?

CVE-2026-39914 is a high-severity missing authorization vulnerability in TIM Flow, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TIM Flow before 26.0.6 contains an improper authorization vulnerability that allows any authenticated user to submit arbitrary SQL queries to a privileged dashboard Excel export endpoint intended for administrative use only. Attackers can craft and submit unauthorized SQL queries to the export endpoint to retrieve sensitive database contents as a downloadable spreadsheet, bypassing role-based access controls.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-39914 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-39914 is a high-severity missing authorization vulnerability in TIM Flow, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-39914 in the wild and no public exploit code.

Affected product: TIM Flow. 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-39914/ (Markdown: https://insights.sbomify.com/CVE-2026-39914/index.md)
```

## Sources

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

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