ENISA and CERT-EU Deploy Frontier AI Models to Automate Code Audits and Uncover Critical Flaws
The European Union Agency for Cybersecurity (ENISA) and CERT-EU confirmed the deployment of advanced OpenAI reasoning models to conduct automated security code analysis across European digital infrastructure projects. The joint initiative uncovered multiple vulnerabilities—including a high-severity flaw tracked as CVE-2026-73431 in open-source tracking software that allowed account takeover via flawed token reuse logic. Similar efforts by national CERT teams and allied agencies under specialized cyber defense access programs, such as OpenAI's Daybreak framework, have systematically surfaced critical flaws in edge platforms and reporting pipelines.
This development marks a decisive turning point for DevSecOps and product security engineering. Security teams have historically relied on rule-based static application security testing (SAST) and dynamic testing (DAST), which often suffer from high false-positive rates and a blind spot for contextual business logic flaws. The successful application of frontier AI models to pinpoint complex architectural logic errors—such as non-expiring recovery tokens and authentication replay conditions—validates agentic code auditing as a viable layer in modern vulnerability management.
Contextually, this initiative fits into a larger race across the software supply chain where the window between vulnerability discovery and weaponization has collapsed. As offensive actors leverage AI assistants to automate reverse engineering and vulnerability scanning, defensive organizations are under acute pressure to achieve proactive parity. Institutional adoption by ENISA signals that AI-augmented code reviews are becoming standard practice for compliance and assurance ahead of pan-European digital governance mandates like the Cyber Resilience Act.
In practice, engineering teams must not treat AI scanners as autonomous replacements for human oversight. European CERTs noted that while models significantly accelerated initial triage and hypothesis generation, security engineers still had to manually validate each exploit path on live staging systems to eliminate hallucinations and verify impact. Platform and DevSecOps leads should begin piloting LLM-based code reviewers directly in pull request workflows to augment SAST pipelines, while establishing strict sandbox verification steps before pushing automated fixes to production.
Read original source