Rust Researcher Builds AI Pipeline to Test 900 Vulnerability Hypotheses Across Crates and Linux Kernel
Sergey Gordeychik, co-founder of CyberOK and SCADA StrangeLove, set out to evaluate remaining classes of bugs in Rust programs after selecting the language for a high-speed packet-processing project. Because the language promises memory safety through ownership, borrowing, and lifetimes, he wanted to understand what errors still occur at crate boundaries and in application logic that the compiler cannot enforce.
He created the Damn Vulnerable Rust Application containing classic issues such as access-control bypasses, OS command injection, SSRF, path traversal, secret leakage, and double-free conditions. A threat model listing concrete prohibitions guided subsequent testing. Initial runs of conventional security tools produced limited results, prompting Gordeychik to integrate LLM-based agents.
The resulting rust-in-peace pipeline runs three independent analysis passes plus a dedicated SAST stage. One pass follows an explicit threat model, another performs blind exploration, and the third replays historical CVE patterns and prior findings. Surviving hypotheses are validated through API tests, fuzzing, or instrumented execution. Failed proof-of-concept attempts feed lessons back into the harness via the LESSONS.md file, which agents consult on later runs.
Early experiments on the vulnerable application achieved 9-of-9 detection once hints were removed and Rust-specific questions added. When applied to real crates, the system surfaced a plausible but ultimately false scenario in x509-parser involving an empty RSA value; the dangerous path was blocked earlier inside asn1-rs. After requiring explicit dependency citations, the pipeline produced actionable results in lopdf and other format parsers.
Across a sample of 50 candidates the three passes generated 80 hits that reduced to 20 confirmed findings after manual triage: 15 with working PoCs and five verified through source analysis. Nine findings appeared in all three passes. The research also contributed a patch to the Linux kernel and was presented at the ZeroNights conference.
Static-analysis coverage was measured with Semgrep and CodeQL rule sets; both showed limited reach against the parser-logic bugs that interested the researcher. The final architecture therefore retains single-pass discoveries rather than relying on majority voting, because eight of the twenty findings would have been lost under a consensus rule.
Related articles
Dart and Flutter SDKs Patch Critical TLS Flaw Tied to Compromised eMudhra Certificates
Dart and Flutter teams released updates to block compromised intermediate certificates from the eMudhra certificate authority. The flaw affects applications built for Android, Windows, and Linux that rely on dart:io for HTTPS connections. Stable releases include Dart 3.13.7 and Flutter 3.47.8, while beta channels received Dart 3.14.0-315.3.beta and Flutter 3.50.0-0.2.pre. The root cause traces to insufficient randomness during key generation for eight eMudhra intermediate CAs disclosed in October 2026. Because dart:io uses its own BoringSSL implementation rather than system revocation lists, applications must be rebuilt and redistributed to users. Additional changes improve root certificate handling on Android 14 and later via Conscrypt APEX modules.
Vulnerability Management Evolution: From Manual Scans to Continuous Threat Exposure Management
This final installment of the Vulnerability Management for Beginners series examines how the discipline has transformed over recent years into an essential component of organizational risk management. The article highlights the dramatic increase in disclosed vulnerabilities, now approaching 48,000 per year, and stresses that fewer than one percent pose real-world risk. It details the shift toward automated asset inventory integrated with SIEM, EDR, and CMDB systems, alongside multi-factor prioritization combining CVSS, EPSS, KEV lists, and FSTEC methodologies. New practices such as EASM, automated penetration testing, BAS, and CTEM are presented as extensions of a mature foundational process rather than replacements. The piece also covers regulatory tightening in Russia through FSTEC Order No. 117, mandatory remediation timelines, and the impact of AI on both defense and attack surfaces. It concludes with a practical Monday-morning action list focused on asset counting, threat feed integration, SLA definition, and cross-team coordination between IT and security.
Fortinet Discloses Eight FortiOS Vulnerabilities Including Three Critical Flaws
Fortinet has published security advisories detailing eight vulnerabilities affecting its FortiOS operating system used in UTM appliances. Three of the issues received the highest severity rating of Critical. CVE-2026-126259 allows unauthenticated command execution with super-admin privileges in FGSP combined with configuration synchronization or auto-scale setups via crafted HA packets. CVE-2026-126254 stems from integer truncation in the BGP daemon and can propagate malicious attributes from configured iBGP peers. CVE-2026-126253 enables authentication bypass in the OSPF daemon, permitting unauthenticated LSA injection. The remaining five vulnerabilities were assigned lower severity ratings. Administrators are urged to apply the available patches promptly.
Microsoft Patches Over 1,000 Vulnerabilities in November 2026 Patch Tuesday Release
Microsoft has issued its November 2026 monthly security updates, addressing a total of 1,093 vulnerabilities across Windows, Office, Azure, SQL Server, SharePoint Server, Exchange Server, and Developer Tools. The update also covers a vulnerability in the third-party Tencent RapidJSON library identified as CVE-2026-124586. Among the fixes, 63 vulnerabilities received the highest severity rating of Critical, while 1,029 were rated Important. Privilege escalation issues accounted for the largest share with 535 cases, followed by 296 remote code execution flaws. Several vulnerabilities have already been confirmed as exploited in the wild. The release follows the standard Patch Tuesday schedule on the second Tuesday of the month.