CVE-2026-62853: ThingLinks vulnerable to authenticated remote code execution via Groovy script registration in ThingLinks
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
ThingLinks is an enterprise IoT platform. Prior to 1.4.0, the `/groovyScriptTest/registerScript` endpoint accepts user-supplied Groovy script content and passes it to an unsandboxed `Groovy compilation and loading` flow. An authenticated attacker can provide code that is compiled and instantiated on the server, resulting in arbitrary server-side code execution. The issue affects the `rule engine`’s Groovy script test/register flow. This issue is fixed in version 1.4.0.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-10-30).
Weakness: CWE-78: Improper Neutralization of Special Elements used in an OS Command (‘OS Command Injection’); CWE-94: Improper Control of Generation of Code (‘Code Injection’)
How it can be exploited
Exploitable over the network with low attack complexity needing low privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 4 references on Exploit Observer
Live scores
- EPSS
- 0.004
low predicted chance of attack - VEDAS
- 0.985
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| mqttsnet thinglinks | version < 1.4.0 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-62853 ThingLinks - Remote Code Execution via Groovy Script. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-62853 ThingLinks - Remote Code Execution via Groovy Script"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/groovyScriptTest/registerScript"; nocase; fast_pattern; classtype:attempted-admin; reference:cve,CVE-2026-62853; reference:url,https://www.exploit.observer/?keyword=CVE-2026-62853&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=thinglinks&match=exact; sid:1104400; rev:1;)
CVE-2026-62853.rules on GitHub
References
Other references
- https://github.com/mqttsnet/thinglinks/security/advisories/GHSA-9vph-5ccx-qp9v (x_refsource_CONFIRM)
- https://github.com/mqttsnet/thinglinks/commit/311ee760dad798f48652722989fcea02349e13a3 (x_refsource_MISC)
- https://github.com/mqttsnet/thinglinks/releases/tag/v1.4.0 (x_refsource_MISC)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
