Loading story…
A critical pre-authentication remote code execution flaw has been publicly disclosed in Plastic SCM / Unity Version Control On-Prem version 11.0.16.10303. The issue stems from insecure default behavior on the service exposed on port 8087: under the default NameWorkingMode, the server accepts username-only authentication, leaks valid local usernames through GetRepositoryServerInfo, and permits any authenticated name to create triggers because the default EVERYBODY ACL grants ALL_PERMISSIONS.
An attacker can chain those conditions to create a malicious server-side trigger and exploit TriggerProcess.ExecuteTrigger, which reportedly passes an attacker-controlled Path directly to Process.Start, leading to code execution as the plasticd service account. The disclosed impact includes full server compromise, arbitrary command execution, repository tampering, source code theft, and persistence on affected version-control infrastructure.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
The Plastic SCM pre-authentication RCE advisory was distributed through the Full Disclosure mailing list, expanding public visibility of the issue. The mailing-list post identified Unity Technologies as the vendor and reiterated the reported impact of full server compromise, repository tampering, source code theft, and persistence.
0day Rubbish Research Team publicly disclosed a pre-authentication remote code execution vulnerability in Plastic SCM / Unity Version Control On-Prem 11.0.16.10303. The advisory described weak default name-only authentication, permissive EVERYBODY ACLs, and trigger execution leading to code execution as the plasticd service account, and it linked a proof of concept and full analysis.
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.
2 references tracked. Mallory keeps watching after this page renders.
seclists.org
Open source0day-rubbish.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.
Dell UnityVSA, the software-defined storage solution from Dell, has been found to contain a critical pre-authentication command injection vulnerability, tracked as CVE-2025-36604. This flaw allows attackers to execute arbitrary commands on affected systems without requiring authentication, significantly increasing the risk of unauthorized access and system compromise. The vulnerability arises from improper handling of login redirect URIs, where user-supplied input is directly concatenated into a command string executed by the system, specifically through Perl’s backtick operator in the getCASURL function. If an attacker crafts a request without the expected authentication cookie, the system’s login flow can be manipulated to inject shell metacharacters, enabling remote code execution. This could allow threat actors to alter system configurations, access or destroy sensitive data, deploy additional malicious scripts, or take full control of the UnityVSA appliance. The issue affects all UnityVSA versions prior to 5.5.1, with Dell’s advisory (DSA-2025-281) confirming that versions 5.5 and earlier are vulnerable. Dell has rated the vulnerability as 'High' severity (CVSS 7.3), but the National Vulnerability Database (NVD) suggests it could reach a 'Critical' rating (CVSS 9.8) under certain conditions. In addition to CVE-2025-36604, related vulnerabilities such as a cross-site scripting flaw (CVE-2025-36605) and other command injection risks in internal utilities have been identified, affecting both Unity and UnityVSA platforms. Security researchers at WatchTowr, who discovered the flaw, have released a Python-based 'Detection Artefact Generator' to help organizations identify vulnerable instances. Both Dell and WatchTowr strongly urge immediate upgrades to UnityVSA version 5.5.1 or later to mitigate the risk. Organizations are also advised to monitor for suspicious redirect URIs, shell executions, and unusual web access behaviors, even after patching. The vulnerability is particularly concerning due to the critical nature of storage systems, which often host sensitive and mission-critical data. Exploitation of this flaw could lead to significant operational disruption and data loss. The disclosure underscores the importance of timely patching and robust monitoring of storage infrastructure. Dell’s response includes detailed mitigation guidance and emphasizes the urgency of remediation. The security community has highlighted the exploit’s simplicity and the potential for widespread impact if left unaddressed. Organizations using UnityVSA should prioritize this update as part of their vulnerability management processes to prevent exploitation and safeguard their data assets.
Jun 29, 2026
A publicly disclosed vulnerability chain in **Stimulsoft Server 2026.3.1** allows an unauthenticated attacker to achieve remote code execution as `NT AUTHORITY\SYSTEM` under the product’s default configuration. According to the advisory, the exposed `/1/signup` endpoint can grant an anonymous user a **Supervisor** account when email activation is disabled, creating an initial privilege path without valid credentials, SMTP access, or administrator involvement. After obtaining Supervisor access, an attacker can upload a malicious `.mrt` report template containing embedded C# code and trigger it through `/1/reporttemplates/<id>/run`. The report engine is said to compile and execute the attacker-controlled script in full trust via `CSharpCodeProvider`, without sandboxing or isolation, causing code to run inside `Stimulsoft.Server.Agent.exe` with SYSTEM privileges and enabling full host compromise. The issue and proof of concept were published by the **0day Rubbish Research Team** and later circulated through Full Disclosure.
Aug 6, 2026
A supply-chain attack against Aqua Security’s **Trivy** ecosystem let attackers publish malicious artifacts and hijack GitHub Action tags, turning a widely used security scanner into a credential stealer. Reporting indicates the intrusion began with abuse of a misconfigured GitHub Actions workflow and theft of privileged credentials, followed by incomplete containment that left residual access in place. Attackers then poisoned **`aquasecurity/trivy-action`** by force-updating 75 of 76 tags, compromised **`setup-trivy`**, and published a backdoored **Trivy `v0.69.4`** release; later activity also pushed malicious Docker Hub images **`0.69.5`** and **`0.69.6`**. The malware harvested GitHub tokens, cloud credentials, SSH keys, Kubernetes secrets, Docker configs, and other CI/CD data from runners and developer environments, encrypted the loot, and exfiltrated it to attacker-controlled infrastructure or fallback GitHub repositories such as **`tpcp-docs`**. Researchers and vendor advisories linked the campaign to **TeamPCP** and described it as an expanding, multi-stage operation that also included a brief OpenVSX compromise of the Trivy VS Code extension, defacement of **44** repositories in Aqua Security’s internal **`aquasec-com`** GitHub organization, and follow-on compromises affecting Checkmarx tooling and the **LiteLLM** PyPI package. Aqua removed malicious artifacts, revoked tokens, restored safe references, and said commercial products were not affected, while GitHub and public advisories identified safe versions including **Trivy `0.69.2`/`0.69.3`**, **`trivy-action` `0.35.0`**, and **`setup-trivy` `0.2.6`**. U.S. CISA added **`CVE-2026-33634`** to the KEV catalog, and incident responders warned organizations that ran affected versions to assume full pipeline compromise, rotate all accessible secrets, audit workflow logs and GitHub activity, and pin GitHub Actions to immutable commit SHAs.
Jul 31, 2026