Live Active security incident? Get immediate response
CVE Record

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

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.

MediumCVSS 5.1Not KEV-listed Updated
Discuss exposure Back to CVEs
Glexia's Take moderate

Analyst readout for executives and security teams

Plain-English summary

CVE-2026-9568 is a reported code injection flaw in ThingsBoard's YAML provisioning path. A remote attacker may be able to abuse gateway Docker Compose generation, but the public record rates exploitation as difficult and high complexity. No source in the bundle confirms active exploitation or an official vendor fix.

Executive priority

Handle as a moderate-priority exposure review, not an emergency patch event based on current evidence. Internet-exposed ThingsBoard instances deserve faster attention because the flaw is remote and involves code injection, even though exploitation is described as difficult and unconfirmed.

Technical view

The reported issue affects getGatewayDockerComposeFile in the /api/v1/provision YAML Handler. It is classified as CWE-74 and CWE-94, with CVSS v2 5.1, network access, no authentication, high complexity, and partial confidentiality, integrity, and availability impact. Source data indicates unresolved vendor response.

Likely exposure

Organizations running ThingsBoard 4.3.1.0 or 4.3.1.1 should prioritize review. Some advisory text claims a wider Community Edition range through 4.3.1.1, but the structured affected list only names 4.3.1.0 and 4.3.1.1, so version scoping needs verification.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. VulDB describes the attack as remotely initiable but difficult, with high complexity. Treat public internet exposure of the provisioning API as higher risk until vendor guidance clarifies exploitability and remediation.

Researcher notes

Evidence is incomplete. The bundle reports no KEV status, no confirmed exploitation, and no official vendor release. The pull request is tagged as patch-related, but the description says the project had not reacted yet. Affected-version statements are not fully consistent across source fields.

Mitigation direction

  • Inventory ThingsBoard deployments and confirm exact versions.
  • Check ThingsBoard vendor guidance and the linked pull request for remediation status.
  • Limit internet exposure to ThingsBoard provisioning endpoints where operationally possible.
  • Apply least-privilege network controls around administrative and provisioning interfaces.
  • Increase monitoring for unusual YAML provisioning or gateway configuration activity.

Validation and detection

  • Confirm whether any deployment runs ThingsBoard 4.3.1.0 or 4.3.1.1.
  • Review whether /api/v1/provision is reachable from untrusted networks.
  • Check logs for unexpected provisioning requests or gateway Docker Compose generation activity.
  • Track the CVE, VulDB entry, and ThingsBoard pull request for changes.
  • Avoid exploit-based validation unless authorized and vendor-safe guidance exists.
Prepared
Confidence
medium
Sources
7

Public sources used

Based on public source material and reviewed before publication.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-74: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-9568 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profile CVE Program record
Severity
Medium
CVSS
5.1 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:H/Au:N/C:P/I:P/A:P/E:ND/RL:ND/RC:UR

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

4 CVSS vectors
6 Timeline events
1 ADP providers
6 Source links

SSVC decision data

CISA-ADP CISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

4 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

Score Version Severity Vector Exploit Impact Source
5.1 CVSS 2.0 Medium AV:N/AC:H/Au:N/C:P/I:P/A:P/E:ND/RL:ND/RC:UR 4.9 6.4 VulDB
5 CVSS 3.1 Medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L/E:X/RL:X/RC:R 1.6 3.4 VulDB
5 CVSS 3.0 Medium CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L/E:X/RL:X/RC:R 1.6 3.4 VulDB
2.3 CVSS 4.0 Low 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 — — VulDB

Vulnerability scoring details

Base CVSS 4.0 score

2.3 Low
CVSS 4.0 vector shape for CVE-2026-9568 Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timeline VulDB

    Advisory disclosed

  2. Source timeline VulDB

    VulDB entry created

  3. CVE reserved CVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timeline VulDB

    VulDB entry last update

  5. CVE published CVE Program

    The CVE record was published.

  6. CVE updated CVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADP CISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

Vendor Product Version / package Status
n/a ThingsBoard 4.3.1.0, 4.3.1.1 Listed
Weakness

CWE details

CWE-74CWE-94

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-74 · source CWE mapping

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligence Same-CWE CVEs
CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligence Same-CWE CVEs