Loading vulnerability details...
| Property | Value |
|---|---|
| Advisory ID | SGZ-2026-8AED8 |
| Severity | HIGH |
| CWE | CWE-119 |
| Confidence | 80% |
| Category | logic_flaw |
| Exploitability | confirmed |
| Package | ex_zapcode@latest (cargo) |
| Location | native/ex_zapcode/src/lib.rs:120 |
| Affected Functions | lock_recover |
| Attack Vector | LOCAL |
| Attack Complexity | LOW |
| Privileges Required | NONE |
| Discovered By | SafeGuard Zero-Day AI Discovery Engine |
The lock_recover function does not properly handle the case where the mutex is poisoned, leading to a potential deadlock.
The vulnerability was identified in the file native/ex_zapcode/src/lib.rs at lines 120 within the ex_zapcode package (version latest). The following functions are directly affected: lock_recover. Any code path that invokes these functions inherits this vulnerability.
File: native/ex_zapcode/src/lib.rs (lines 120)
fn lock_recover<T>(m: &Mutex<T>) -> MutexGuard<'_, T> { m.lock().unwrap_or_else(|p| p.into_inner()) }
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.
An attacker can exploit this vulnerability by creating a poisoned mutex and then calling lock_recover on it.
A deadlock can occur, causing the program to hang indefinitely.
The lock_recover function should be modified to properly handle the case where the mutex is poisoned.
Advisory: SGZ-2026-8AED8 | 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-8AED8 |
| Severity | HIGH |
| CWE | CWE-119 |
| Confidence | 80% |
| Category | logic_flaw |
| Exploitability | confirmed |
| Package | ex_zapcode@latest (cargo) |
| Location | native/ex_zapcode/src/lib.rs:120 |
| Affected Functions | lock_recover |
| Attack Vector | LOCAL |
| Attack Complexity | LOW |
| Privileges Required | NONE |
| Discovered By | SafeGuard Zero-Day AI Discovery Engine |
The lock_recover function does not properly handle the case where the mutex is poisoned, leading to a potential deadlock.
The vulnerability was identified in the file native/ex_zapcode/src/lib.rs at lines 120 within the ex_zapcode package (version latest). The following functions are directly affected: lock_recover. Any code path that invokes these functions inherits this vulnerability.
File: native/ex_zapcode/src/lib.rs (lines 120)
fn lock_recover<T>(m: &Mutex<T>) -> MutexGuard<'_, T> { m.lock().unwrap_or_else(|p| p.into_inner()) }
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.
An attacker can exploit this vulnerability by creating a poisoned mutex and then calling lock_recover on it.
A deadlock can occur, causing the program to hang indefinitely.
The lock_recover function should be modified to properly handle the case where the mutex is poisoned.
Advisory: SGZ-2026-8AED8 | 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