ThingLinks vulnerable to authenticated remote code execution via Groovy script registration in ThingLinks
Affects ThingLinks versions before 1.4.0 through the rule engine's Groovy script test/register flow. The fix is in 1.4.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.4.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
ThingLinks, an enterprise IoT platform, is affected through its Groovy script registration feature in the rule engine. An authenticated user can submit Groovy code that the server compiles and runs without restriction, allowing them to execute arbitrary code on the server.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- mqttsnet thinglinks
fixed in 1.4.0
References 3
GitHub · mqttsnet/thinglinks
Questions about CVE-2026-62853
What does this mean?
An authenticated user can supply Groovy code through the rule engine's script test/register flow. The server compiles and runs that code, which gives arbitrary code execution on the server.Source: github.com
Am I affected, and how do I check?
ThingLinks versions prior to 1.4.0 are affected, and the issue is in the rule engine Groovy script test/register flow. Check the installed ThingLinks version against that range to see which version applies.Source: github.com
What should I do about it?
Upgrade ThingLinks to 1.4.0 or later, the fixed version listed for this issue.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data