Habr•October 2, 2026•🇷🇺Translated from Russian

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

Security NEXT•Vulnerabilities & Exploits

GitLab Issues Critical Patches for CVE-2026-110264 Affecting Wide Range of Versions

GitLab has released emergency security updates to address multiple vulnerabilities, including one rated critical that allows unauthenticated remote code execution. The flaw, tracked as CVE-2026-110264, stems from an integer overflow in the regular expression compiler and carries a maximum CVSSv3.1 base score of 10.0. It impacts GitLab Community Edition and Enterprise Edition starting from version 7.0, with patches now available for both current and older branches. The company strongly urges immediate updates due to the severity and potential for arbitrary code execution on affected servers. Additional lower-severity issues were also resolved in the same release cycle.

Hispasec•Vulnerabilities & Exploits

PHP Issues Emergency Patches for Critical PHP2Shell RCE Flaws as Exploit Attempts Emerge

PHP has released urgent patches for two critical vulnerabilities collectively known as PHP2Shell that enable unauthenticated remote code execution on affected servers. The flaws, tracked as CVE-2026-109618 and CVE-2026-109619, score 9.2 on CVSS v4.0 and have already seen active exploitation attempts with malicious payloads adjusted to bypass WAF rules. The issues affect multiple PHP deployment methods including Apache with mod_php, PHP-FPM, php-cgi, FrankenPHP, and LiteSpeed, and do not require complex application code to be exploitable. CVE-2026-109618 involves a memory corruption chain leading to code execution under the web process privileges, while CVE-2026-109619 stems from an obsolete global state issue causing use-after-free conditions that can result in memory disclosure and code execution. Patched versions include PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35, with administrators advised to restart all persistent workers after updating. Temporary mitigations such as setting memory_limit to -1 and disabling session.upload_progress.enabled are available for environments that cannot patch immediately.

Security NEXT•Vulnerabilities & Exploits

Two Critical RCE Vulnerabilities Patched in PHP with CVSS 9.2 Scores

The PHP development team has disclosed two severe remote code execution vulnerabilities affecting the widely used scripting language. Both issues, tracked as CVE-2026-109618 and CVE-2026-109619, received a CVSSv4.0 base score of 9.2 and were rated Critical. The flaws stem from improper memory handling during request processing and cleanup phases. Exploitation could allow attackers to execute arbitrary code by manipulating uninitialized or residual data in worker processes. Security updates addressing both vulnerabilities were released on October 21, 2026, and users are strongly urged to apply the patches immediately. The advisories were previewed the previous day, highlighting the urgency of the fixes.

BoletimSec•Vulnerabilities & Exploits

Critical PHP Core Flaws Enable Unauthenticated Remote Code Execution

The PHP project released emergency patches on October 21 for two critical vulnerabilities in the language core, tracked as CVE-2026-109618 and CVE-2026-109619 and collectively referred to as PHP2Shell. Both issues received a CVSS 4.0 score of 9.2 and allow remote code execution without authentication. CVE-2026-109618 resides in memory-handling routines where longjmp can leave request data partially initialized, and subsequent shutdown operates on invalid data; multipart requests with many headers or empty file fields can trigger the condition. CVE-2026-109619 affects an obsolete global state in long-lived workers that retain references to freed memory, with confirmed paths involving fatal errors, error reporting data, and session upload progress. Researchers demonstrated unauthenticated code execution over HTTP against the first flaw on Apache with mod_php using default limits, while PHP-FPM exposure was identified through code analysis. The FBI Cyber Division issued an alert urging immediate updates, and Cloudflare deployed WAF rules while confirming early attacks in the wild.