# CVE-2026-109526: HBAI-Ltd Toonflow-app exportData Endpoint information disclosure


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-4466-r6c7-638c

## What is CVE-2026-109526?

CVE-2026-109526 is a medium-severity vulnerability in HBAI-Ltd Toonflow-app, published on 13 Oct 2026. 

### Official description

A vulnerability has been found in HBAI-Ltd Toonflow-app up to 1.1.8. This affects an unknown function of the component exportData Endpoint. Such manipulation leads to information disclosure. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.0 mitigates this issue. It is advisable to upgrade the affected component. The vendor explains: "The report targets ToonFlow version 1.1.8. The current release is 2.0.4, which is the result of a substantial architectural refactor; the code paths referenced in the report do not apply to the current version. The report does not describe a vulnerability in any supported release."

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-109526 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109526 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109526 is a medium-severity vulnerability in HBAI-Ltd Toonflow-app, published on 13 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109526 exists.

Affected product: HBAI-Ltd Toonflow-app. 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-109526/ (Markdown: https://insights.sbomify.com/CVE-2026-109526/index.md)
```

## Sources

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

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