# CVE-2026-9568: ThingsBoard YAML provision getGatewayDockerComposeFile code injection

> Remote attackers can inject code via the YAML provision handler in ThingsBoard, potentially leading to arbitrary code execution.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-96jf-2v3w-hrrp

## What is CVE-2026-9568?

CVE-2026-9568 is a low-severity code injection vulnerability in ThingsBoard, published on 26 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A weakness has been identified in ThingsBoard up to 4.3.1.1. Affected by this vulnerability is the function getGatewayDockerComposeFile of the file /api/v1/provision of the component YAML Handler. This manipulation causes code injection. It is possible to initiate the attack remotely. The attack's complexity is rated as high. The exploitation appears to be difficult. The project was informed of the problem early through a pull request but has not reacted yet.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-9568 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9568 is a low-severity code injection vulnerability in ThingsBoard, published on 26 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-9568 in the wild and no public exploit code.

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

## Sources

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

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