Loading story…
Trail of Bits found a high-severity underconstrained-input vulnerability in Miden’s zero-knowledge virtual machine core cryptographic library that could let a malicious prover forge Falcon signatures and steal funds from accounts using Falcon key pairs. The flaw in the MASM mod_12289 procedure allowed a prover-supplied remainder to reach a 32-bit subtraction without first being validated as a 64-bit value.
Auditors developed AI-assisted tooling for the MASM-based stack, including a language server, decompiler, static-analysis engine, linter, and Lean formal model of the VM executor. The static analysis identified more than 400 publicly reachable instances of insufficient type validation, while formal verification generated 95 machine-checked proofs and found additional defects in rotr and wrapping_mul; Miden has adopted the static-analysis engine for future core-library changes.
Track how attackers are adapting to this technology.
5 events from the most recent confirmed update back to the earliest known activity.
Trail of Bits' Lean model and MASM translator generated 95 machine-checked proofs and found bugs in the 64-bit rotr and 256-bit wrapping_mul procedures that existing unit tests had not detected.
Reviewers found a high-severity underconstrained prover-advice vulnerability in mod_12289: an unvalidated remainder could cause an incorrect modular-reduction result. A malicious prover could use the flaw to forge Falcon signatures and drain Miden accounts controlled by Falcon key pairs.
AI-assisted static analysis identified more than 400 unique publicly reachable locations in the Miden core library where type validation could be improved.
The Miden team commissioned Trail of Bits to review parts of the Miden zero-knowledge VM and its MASM-based cryptographic core library before launch.
The Miden team adopted the static-analysis engine developed during the review to help secure future changes to the Miden core library.
Follow how adversaries are adapting to this technology, and where it touches your stack today.
2 references tracked. Mallory keeps watching after this page renders.
Map 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.
wolfSSL fixed two flaws in its hand-optimized ML-KEM-1024 SIMD decapsulation code that can permit near-complete private-key recovery when static ML-KEM keys are reused and an attacker can access a plaintext-checking or decapsulation oracle. **CVE-2026-10097** affects AVX2 builds by omitting comparison of the final 32 bytes of a 1,568-byte ciphertext, while **CVE-2026-6330** affects ARM64 NEON builds by leaving approximately half the ciphertext unchecked. Researchers reported recovery of 98.0% of secret coefficients with 400 chosen ciphertexts on AVX2 and 98.5% with 600 on NEON; wolfSSL addressed both issues in version 5.9.2. The defects are implementation failures in wolfSSL’s independently written SIMD Fujisaki–Okamoto ciphertext validation, not a break of ML-KEM or FIPS 203. They add to prior evidence that post-quantum cryptographic deployments remain exposed to implementation-level side channels: the KyberSlash research found secret-dependent timing behavior in several Kyber/ML-KEM implementations, including reference code, that enabled practical secret-key recovery on Raspberry Pi 2 and Arm Cortex-M4 systems. Organizations using wolfSSL should upgrade to 5.9.2 or later, identify long-lived static ML-KEM keys on affected AVX2 or NEON systems, and prioritize rotation of potentially exposed keys; TLS 1.3 deployments using freshly generated ephemeral hybrid ML-KEM keys are not susceptible to this key-recovery attack.
Sep 13, 2026
Researchers at **CISPA Helmholtz Center for Information Security** disclosed **StackWarp** (**CVE-2025-29943**), a microarchitectural weakness affecting **AMD Zen** CPUs that can undermine the integrity guarantees of **AMD SEV-SNP** “confidential VM” protections. The attack model assumes a **malicious insider with host/hypervisor control** who can run a parallel hyperthread and exploit a previously undocumented hypervisor-side control bit to manipulate the protected guest’s stack pointer behavior, particularly when **Simultaneous Multithreading (SMT)** is enabled. Reported impacts include the ability to recover sensitive data from SEV-SNP guests—such as **cryptographic private keys**—and to enable follow-on compromise scenarios like **bypassing OpenSSH password authentication** and **privilege escalation** within the VM. AMD issued patches (made available in **July 2025**) and later published a security bulletin rating the issue **low severity**, but the disclosure highlights ongoing risk that confidential computing isolation can be weakened by CPU-level behaviors; organizations running SEV-SNP should prioritize applying AMD’s updates and review SMT-related exposure in multi-tenant or high-trust boundary environments.
Jun 29, 2026
A critical vulnerability (CVE-2025-12816) was discovered in the popular JavaScript cryptography library *node-forge*, which is downloaded over 20 million times per week. The flaw allows attackers to bypass signature verification by exploiting an interpretation-conflict in the library's ASN.1 validation mechanism, enabling malformed data to pass as valid even when cryptographically invalid. This vulnerability could allow unauthenticated attackers to craft ASN.1 structures that desynchronize schema validations, potentially bypassing cryptographic verifications and security decisions in applications relying on node-forge. The issue was responsibly disclosed by a researcher from Palo Alto Networks, and a fix was released in version 1.3.2 of node-forge. Security advisories from CERT-CC warn that the impact varies by application, but may include authentication bypass, signed data tampering, and misuse of certificate-related functions. Developers using node-forge are strongly advised to update to the latest version immediately to mitigate the risk, as the vulnerability could have significant consequences in environments where cryptographic verification is central to trust decisions.
Jun 29, 2026