Loading story…
TinaCMS disclosed and patched a remote code execution vulnerability in @tinacms/cli affecting the Forestry-to-Tina migration workflow. The flaw allowed attacker-controlled values from .forestry YAML files—particularly label and name fields—to be injected into generated tina/templates.{ts,js} source files through an unsafe internal marker mechanism in addVariablesToCode. Because those generated files are then imported by tina/config.{ts,js}, malicious JavaScript could execute as soon as a developer ran Tina development or build commands, making the issue exploitable with no authentication but requiring a victim to migrate a malicious Forestry project and then start Tina.
The fix was released in @tinacms/cli 2.4.3 and hardens code generation against untrusted input. TinaCMS replaced the forgeable static __TINA_INTERNAL__ marker with a per-process random nonce-based marker so only generator-created placeholders are converted back into raw code after JSON.stringify, and added validation to reject unexpected control characters such as NUL bytes and newlines in Forestry names and labels. The patch also included regression tests to ensure legitimate generated markers are unquoted while user-controlled look-alike strings remain inert data.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
A GitHub security advisory disclosed a remote code execution vulnerability in @tinacms/cli's Forestry-to-Tina migration workflow, where unsanitized values from .forestry YAML files could inject arbitrary JavaScript into generated Tina source files. The advisory said the issue was verified end-to-end against tinacms and @tinacms/cli version 2.3.1 and noted code would execute when a developer ran tinacms dev or tinacms build after migrating a malicious project.
TinaCMS released @tinacms/cli version 2.4.3, highlighting a security-relevant patch that hardens Forestry migration code generation against untrusted input. The release also updated dependencies including tinacms 3.9.0 and @tinacms/app 2.5.3.
A code change was committed to harden TinaCMS's Forestry migration generator against untrusted input by replacing a forgeable internal marker with a per-process random nonce-based marker and rejecting unexpected control characters in Forestry names and labels. The commit also added regression tests to ensure attacker-controlled look-alike strings remain inert data.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
github.com
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Several server and developer administration tools have disclosed severe code-execution vulnerabilities affecting exposed management functionality. **Termix** reported an authenticated OS command injection in `GET /ssh/file_manager/ssh/resolvePath`, where double-quoted user input allowed shell substitution via ``$(...)`` and backticks, enabling arbitrary commands on the connected remote host under the active SSH account. A separate **Termix** issue, tracked as `CVE-2026-45746`, affected versions prior to **2.3.2** and allowed attackers to tamper with a client-controlled `sessionId` to access other users' active File Manager SSH sessions, potentially leading to unauthorized file operations and remote code execution on another user's VPS. Other disclosures showed similar high-impact flaws in JavaScript-based backends. **DbGate** fixed an RCE in **v7.1.9** after researchers found that `POST /runners/start` and `POST /runners/load-reader` concatenated attacker-controlled values into generated JavaScript executed by a forked Node.js process; in anonymous-auth deployments, the issue could permit **unauthenticated RCE**. **BrowserStack Runner** through **0.9.5** was assigned `CVE-2026-49143` for an unauthenticated RCE in the `/_log` handler, where crafted JSON passed through `vm.runInNewContext()` and `eval()` allowed attackers to escape the sandbox and invoke `child_process` on reachable runner instances.
Jun 29, 2026
A **critical remote code execution** issue in the *n8n* open-source workflow automation platform, tracked as **CVE-2026-25049** (also published as **GHSA-6cqr-8cfr-67f8**), allows an **authenticated** user with permission to create or modify workflows to escape n8n’s expression sandbox and execute arbitrary system commands on the underlying host. The flaw stems from **insufficient input sanitization/weak sandboxing** in n8n’s expression evaluation (server-side JavaScript) and was identified during follow-up analysis after an earlier critical n8n vulnerability (**CVE-2025-68613**) was patched; researchers report the new issue effectively **bypasses prior mitigations**. Reporting indicates exploitation can lead to **full compromise** of the n8n instance, including access to the filesystem and the ability to **steal stored credentials and secrets** (e.g., API keys, OAuth tokens) and sensitive configuration, with potential for **pivoting** into connected internal services and cloud accounts in multi-tenant deployments. Public reporting also notes **public exploits** are available. n8n maintainers state the issue is patched, and affected organizations should upgrade to fixed releases (**1.123.17** and **2.5.2**), as versions **prior to 1.123.17 and 2.5.2** are impacted.
Jun 29, 2026
A critical **server-side template injection** flaw tracked as `CVE-2026-54390` affects **JTL Shop** versions **5.2.0 through 5.7.1**, where unsanitized user input is passed to the **Smarty** template engine. The vulnerability allows **unauthenticated remote attackers** to inject malicious template syntax and access sensitive server-side information, including **database credentials** and **encryption keys**. On **JTL Shop 5.4.0 through 5.7.1**, the flaw can be escalated to **remote code execution** by abusing registered Smarty modifiers such as `unserialize` and `file_get_contents` to write a **webshell** into the web root and run arbitrary commands as the web server user. The issue has been rated **critical** with **CVSS 3.1 9.8** and **CVSS 4.0 9.3**, and affected organizations are advised to upgrade to **JTL Shop 5.7.2 or later** and ensure user input reaching the template engine is properly sanitized.
Jun 29, 2026