Loading vulnerability details...
| Property | Value |
|---|---|
| Advisory ID | SGZ-2026-116B7 |
| Severity | HIGH |
| CWE | CWE-78 |
| Confidence | 78% |
| Category | injection |
| Exploitability | likely |
| Package | ACE@latest (python) |
| Location | ACE/bin/make_release.py:22-28 |
| Attack Vector | NETWORK |
| Attack Complexity | LOW |
| Privileges Required | LOW |
| Discovered By | SafeGuard Zero-Day AI Discovery Engine |
The make_release.py script constructs shell commands using user-supplied command-line options and executes them via subprocess without proper sanitization, allowing an attacker to inject arbitrary commands.
The vulnerability was identified in the file ACE/bin/make_release.py at lines 22-28 within the ACE package (version latest). Any code path that invokes these functions inherits this vulnerability.
File: ACE/bin/make_release.py (lines 22-28)
subprocess.check_call(shlex.split(command)) # command built from opts.release_dir
The code above demonstrates the vulnerable pattern. This code is executed at runtime and can be directly exploited by an attacker with the appropriate access level.
Supply a malicious value for the --release-dir option that includes a semicolon or && to execute additional commands.
Arbitrary code execution on the host running the release script, potentially compromising the build environment.
Avoid using shell=True; validate and sanitize all inputs; use subprocess.run with a list of arguments built from trusted sources.
Advisory: SGZ-2026-116B7 | Source: SafeGuard Zero-Day AI Discovery | Status: Candidate
This vulnerability was autonomously discovered by SafeGuard's AI-powered Zero-Day Discovery engine using TAOR (Think-Act-Observe-Repeat) agentic analysis on the package source code. It is not yet tracked in any public vulnerability database (CVE, NVD, GHSA, OSV). This finding should be triaged by a security engineer and, if confirmed, reported upstream to the package maintainer.
| Property | Value |
|---|---|
| Advisory ID | SGZ-2026-116B7 |
| Severity | HIGH |
| CWE | CWE-78 |
| Confidence | 78% |
| Category | injection |
| Exploitability | likely |
| Package | ACE@latest (python) |
| Location | ACE/bin/make_release.py:22-28 |
| Attack Vector | NETWORK |
| Attack Complexity | LOW |
| Privileges Required | LOW |
| Discovered By | SafeGuard Zero-Day AI Discovery Engine |
The make_release.py script constructs shell commands using user-supplied command-line options and executes them via subprocess without proper sanitization, allowing an attacker to inject arbitrary commands.
The vulnerability was identified in the file ACE/bin/make_release.py at lines 22-28 within the ACE package (version latest). Any code path that invokes these functions inherits this vulnerability.
File: ACE/bin/make_release.py (lines 22-28)
subprocess.check_call(shlex.split(command)) # command built from opts.release_dir
The code above demonstrates the vulnerable pattern. This code is executed at runtime and can be directly exploited by an attacker with the appropriate access level.
Supply a malicious value for the --release-dir option that includes a semicolon or && to execute additional commands.
Arbitrary code execution on the host running the release script, potentially compromising the build environment.
Avoid using shell=True; validate and sanitize all inputs; use subprocess.run with a list of arguments built from trusted sources.
Advisory: SGZ-2026-116B7 | Source: SafeGuard Zero-Day AI Discovery | Status: Candidate
This vulnerability was autonomously discovered by SafeGuard's AI-powered Zero-Day Discovery engine using TAOR (Think-Act-Observe-Repeat) agentic analysis on the package source code. It is not yet tracked in any public vulnerability database (CVE, NVD, GHSA, OSV). This finding should be triaged by a security engineer and, if confirmed, reported upstream to the package maintainer. This vulnerability involves weaknesses in
This high-severity vulnerability could allow attackers to gain unauthorized access, execute arbitrary code, or compromise data integrity. Prompt remediation is strongly recommended.
Isolate affected systems from untrusted networks until patching is complete
Implement enhanced monitoring for exploitation attempts and unusual behavior