Google Releases "Mantis," an Open-Source Framework That Automates Vulnerability Discovery Through Remediation — Cutting Token Overhead by Over 85%

On September 2, 2026, Google unveiled Mantis, an open-source framework that uses AI to automate the entire software vulnerability lifecycle—from discovery and candidate triage to reproduction and remediation. The framework addresses the challenge of low-precision AI code scanning, where true positive rates can fall below 7%, by employing multiple AI agents for layered verification and reproducing vulnerabilities in isolated sandbox environments before generating remediation code. Mantis uses hierarchical security summarization to reduce token overhead by over 85% while preserving critical structural information, enabling large-scale repository analysis. It is accessible via Gemini CLI and Antigravity CLI, and includes "mantis-advise" for development-time guidance based on historical vulnerability data. Concurrently, Google announced "Gemini 3.8 Flash Cyber," a security-specialized AI model that improved patch accuracy by 2.6x within the Chrome team and discovered a critical vulnerability in just two hours during cloud team testing. The model is currently available only to trusted testers and government agencies. Google cautions that AI-generated reports and code require manual review and should be tested in isolated environments, recommending developers provide appropriate context and maintain clear vulnerability criteria to maximize the value of AI-driven discovery. 

https://finance.biggo.com/news/31549d83-817f-4af0-885c-203a1a869975

Comments

Post a Comment

Popular posts from this blog

Prompt Engineering Demands Rigorous Evaluation

In the blog post “Prompt Engineering Requires Evaluation” on the Shostack + Associates website, the author argues that treating prompts for large language models (LLMs) merely as creative artefacts is insufficient. Engineering prompts properly demands structured evaluation frameworks — what the AI community calls “evals” — to test which prompt versions work better, with which models, and under which conditions. The post highlights that simply assuming a prompt is “good enough” creates risks when LLMs are integrated into production systems (e.g., for threat modeling). It advocates for measuring prompt performance, variation effects, and tool-chain dependencies (model, context, ancillary materials).  Ultimately the message is: prompt engineering should borrow disciplined practices from software engineering (versioning, testing, benchmarking) rather than relying on informal experimentation.  https://shostack.org/blog/prompt-enignieering-requires-evaluation/
Read more

OWASP ASVS 5.0 Released - Key Updates and What You Need to Know

The OWASP Foundation has released version 5.0 of the Application Security Verification Standard (ASVS), a major update to their security framework for web applications. This new version features restructured security requirements for better clarity, expanded guidance for cloud and API security, improved DevSecOps integration for CI/CD pipelines, updated threat modeling support, and enhanced compliance mapping with standards like NIST and PCI DSS. ASVS serves as a critical benchmark for developers building secure applications, penetration testers conducting security assessments, and auditors performing compliance reviews.  The standard is available for download from the OWASP ASVS project page, with organizations encouraged to integrate it into their software development lifecycles through code reviews and security testing tools. As a vendor-neutral, community-driven project, OWASP continues to welcome contributions to further develop the standard. This release represents an importa...
Read more

Open-SPDD proposes an open framework for Spec-Driven Development workflows

Open-SPDD is an open-source project focused on Spec-Driven Product Development, aiming to formalize how software specifications, requirements, architecture, and implementation interact throughout the development lifecycle. The project promotes structured specification management, traceability, and AI-assisted engineering workflows, positioning itself as a foundation for “SpecOps”-style development practices. Its GitHub materials describe SPDD as a way to reduce ambiguity between planning and execution by treating specifications as first-class operational artifacts that can drive automation, validation, and collaboration across engineering teams  https://github.com/gszhangwei/open-spdd
Read more