CVE-2025-34282: ThingsBoard · Server-Side Request Forgery (SSRF)
Affects ThingsBoardSource CVE Database V5
Not known to be exploited · public exploit available (Exploit-DB) · CVSS 6.9 Medium : upgrade to 4.2.1 as a priority.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 1.8% chance of exploitation in 30 days – higher than 78% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.2.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:LExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 17 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by VulnCheck
, 185 days before disclosure
CVE published
on cve.org
, t = 0
In Threat Radar
record ingested
, 13 minutes after disclosure
First Exploit-DB entry (opens in a new tab)
ThingsBoard IoT Platform 4.2.0 - Server-Side Request Forgery (SSRF)
, 202 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade thingsboard/thingsboard to 4.2.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubthingsboard/thingsboardpkg:github/thingsboard/thingsboardOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix for this vulnerability is available in ThingsBoard version 4.2.1 and later. Users should upgrade to version 4.2.1 or newer to remediate this issue.
Description
ThingsBoard versions < 4.2.1 contain a server-side request forgery (SSRF) vulnerability in the dashboard's Image Upload Gallery feature. An attacker can upload a malicious SVG file that references a remote URL. If the server processes the SVG file in a way that parses external references, it may initiate unintended outbound requests. This can be used to access internal services or resources.