CVE-2026-9568

MEDIUMNVD 5.05.0—
EchelonGraph scoreMEDIUM confidence

Score 5.0 from GitHub Security Advisory (severity: LOW) published 2026-05-26. NVD baseline CVSS 5.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.0
EG Score
5.0(medium)
EPSS
12.3%
KEV
Not listed

Published

May 26, 2026

Last Modified

May 26, 2026

Advisory Details (2)

Auto-updated Jun 15, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

Hardened device credentials validation

Fix merged in thingsboard/thingsboard PR #15550 on 2026-06-09 — awaiting tagged release

https://github.com/thingsboard/thingsboard/pull/15550
generic

GitHub - thingsboard/thingsboard: Open-source IoT Platform - Device management, data collection, processing and visualization. · GitHub

https://github.com/thingsboard/thingsboard/

Vendor Advisories for CVE-2026-9568(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 17:03 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-13 22:31 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-08 15:16 UTCEPSS rescore
  10. 2026-07-07 13:46 UTCEPSS rescore
  11. 2026-07-06 16:27 UTCEPSS rescore
  12. 2026-07-06 02:23 UTCEPSS rescore
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-01 15:07 UTCEPSS rescore
  16. 2026-07-01 12:27 UTCGHSA enrichment
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-28 22:57 UTCGHSA enrichment
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-27 18:52 UTCGHSA enrichment
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-26 17:33 UTCGHSA enrichment
  25. 2026-06-25 13:50 UTCEPSS rescore
Show 49 more
  1. 2026-06-25 11:18 UTCGHSA enrichment
  2. 2026-06-24 14:05 UTCEPSS rescore
  3. 2026-06-23 21:33 UTCEPSS rescore
  4. 2026-06-22 14:25 UTCEPSS rescore
  5. 2026-06-21 14:56 UTCEPSS rescore
  6. 2026-06-21 01:59 UTCEPSS rescore
  7. 2026-06-19 19:26 UTCEPSS rescore
  8. 2026-06-18 17:52 UTCEPSS rescore
  9. 2026-06-17 19:13 UTCGHSA enrichment
  10. 2026-06-17 17:53 UTCEPSS rescore
  11. 2026-06-16 17:53 UTCEPSS rescore
  12. 2026-06-16 16:51 UTCGHSA enrichment
  13. 2026-06-15 17:49 UTCEPSS rescore
  14. 2026-06-15 13:41 UTCGHSA enrichment
  15. 2026-06-14 23:18 UTCEPSS rescore
  16. 2026-06-14 08:35 UTCGHSA enrichment
  17. 2026-06-13 23:00 UTCEPSS rescore
  18. 2026-06-13 08:04 UTCGHSA enrichment
  19. 2026-06-12 23:12 UTCEPSS rescore
  20. 2026-06-12 23:12 UTCEPSS rescore
  21. 2026-06-12 07:34 UTCGHSA enrichment
  22. 2026-06-11 14:00 UTCEPSS rescore
  23. 2026-06-11 07:04 UTCGHSA enrichment
  24. 2026-06-10 22:19 UTCEPSS rescore
  25. 2026-06-10 13:22 UTCEPSS rescore
  26. 2026-06-10 06:34 UTCGHSA enrichment
  27. 2026-06-09 06:04 UTCGHSA enrichment
  28. 2026-06-08 14:17 UTCEPSS rescore
  29. 2026-06-08 05:33 UTCGHSA enrichment
  30. 2026-06-07 15:25 UTCEPSS rescore
  31. 2026-06-07 05:03 UTCGHSA enrichment
  32. 2026-06-06 13:47 UTCEPSS rescore
  33. 2026-06-06 04:33 UTCGHSA enrichment
  34. 2026-06-05 22:47 UTCEPSS rescore
  35. 2026-06-05 06:10 UTCEPSS rescore
  36. 2026-06-05 04:03 UTCGHSA enrichment
  37. 2026-06-04 13:12 UTCEPSS rescore
  38. 2026-06-04 03:33 UTCGHSA enrichment
  39. 2026-06-03 03:02 UTCGHSA enrichment
  40. 2026-06-02 20:13 UTCEPSS rescore
  41. 2026-06-02 02:32 UTCGHSA enrichment
  42. 2026-06-01 13:52 UTCEPSS rescore
  43. 2026-06-01 02:01 UTCGHSA enrichment
  44. 2026-05-31 22:30 UTCEPSS rescore
  45. 2026-05-31 00:16 UTCEPSS rescore
  46. 2026-05-29 13:44 UTCEPSS rescore
  47. 2026-05-28 13:44 UTCEPSS rescore
  48. 2026-05-27 13:40 UTCEPSS rescore
  49. 2026-05-26 18:56 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9568?
CVE-2026-9568 is a medium vulnerability published on May 26, 2026. 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…
When was CVE-2026-9568 disclosed?
CVE-2026-9568 was first published in the National Vulnerability Database on May 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9568 actively exploited?
CVE-2026-9568 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9568?
CVE-2026-9568 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2026-9568?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9568, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-9568

Explore →

Is Your Infrastructure Affected by CVE-2026-9568?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs