Loading vulnerability details...
| Property | Value |
|---|---|
| Advisory ID | SGZ-2026-6A6DB |
| Severity | HIGH |
| CWE | CWE-94 |
| Confidence | 80% |
| Category | injection |
| Exploitability | likely |
| Package | arf-console@latest (cargo) |
| Location | crates/arf-console/src/cli.rs:13-16 |
| Attack Vector | LOCAL |
| Attack Complexity | LOW |
| Privileges Required | LOW |
| Discovered By | SafeGuard Zero-Day AI Discovery Engine |
The CLI accepts an arbitrary R expression via the --eval flag and forwards it to the embedded R interpreter without any validation or sandboxing. An attacker can supply malicious R code that gets executed with the privileges of the user running the CLI, leading to arbitrary code execution.
The vulnerability was identified in the file crates/arf-console/src/cli.rs at lines 13-16 within the arf-console package (version latest). Any code path that invokes these functions inherits this vulnerability.
File: crates/arf-console/src/cli.rs (lines 13-16)
#[arg(short = 'e', long = "eval")]
pub eval: Option<String>,
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.
User supplies malicious R code via --eval which is passed directly to the R engine, allowing execution of arbitrary commands or system calls.
Remote code execution on the host running the CLI, potentially leading to full system compromise.
Validate or sandbox the supplied R code, restrict to a safe subset, or avoid direct evaluation. Consider using a whitelist of allowed functions or running the R code in a restricted environment.
Advisory: SGZ-2026-6A6DB | 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-6A6DB |
| Severity | HIGH |
| CWE | CWE-94 |
| Confidence | 80% |
| Category | injection |
| Exploitability | likely |
| Package | arf-console@latest (cargo) |
| Location | crates/arf-console/src/cli.rs:13-16 |
| Attack Vector | LOCAL |
| Attack Complexity | LOW |
| Privileges Required | LOW |
| Discovered By | SafeGuard Zero-Day AI Discovery Engine |
The CLI accepts an arbitrary R expression via the --eval flag and forwards it to the embedded R interpreter without any validation or sandboxing. An attacker can supply malicious R code that gets executed with the privileges of the user running the CLI, leading to arbitrary code execution.
The vulnerability was identified in the file crates/arf-console/src/cli.rs at lines 13-16 within the arf-console package (version latest). Any code path that invokes these functions inherits this vulnerability.
File: crates/arf-console/src/cli.rs (lines 13-16)
#[arg(short = 'e', long = "eval")]
pub eval: Option<String>,
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.
User supplies malicious R code via --eval which is passed directly to the R engine, allowing execution of arbitrary commands or system calls.
Remote code execution on the host running the CLI, potentially leading to full system compromise.
Validate or sandbox the supplied R code, restrict to a safe subset, or avoid direct evaluation. Consider using a whitelist of allowed functions or running the R code in a restricted environment.
Advisory: SGZ-2026-6A6DB | 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