Cisco released Antares on July 21, 2026, a family of small language models built specifically for vulnerability localization, the job of pointing analysts at the source files most likely to contain a known flaw. The first two checkpoints, Antares-350M and Antares-1B, are published as open-weight models on Hugging Face, and Cisco says they match or beat much larger closed and open-weight systems on this task while costing far less to run. A third model, Antares-3B, is listed as in progress. Because the models are small enough to run locally, organizations can audit proprietary repositories without pushing source code to an external service.
Why this changes what a security audit should look for
Most public coverage of AI for security focuses on chatbot-style assistants or general coding copilots. Antares targets a narrower workflow: given a vulnerability description, a CWE category, or an advisory, which files in a repository should a human reviewer actually open? That question sits at the front of any audit, because triage is where analyst hours get spent. If a small, locally hostable model can produce a credible ranked shortlist, the audit process changes in practical ways:
- Continuous scanning becomes cheap enough to attach to every commit, not every release.
- Audit scopes can widen from quarterly reviews to per-change reviews.
- Sensitive codebases, such as those in healthcare, defense, finance, or public-sector environments, can be reviewed by AI without leaving the internal network.
- Smaller teams, including universities and nonprofits, can run the same triage playbooks as larger security organizations.
How the models actually work
Antares uses an iterative search pattern modeled on how a human investigator moves through a repository. Starting from a vulnerability description, the model looks for code that matches, opens candidate files, folds new evidence into its reasoning, backtracks when a path is unproductive, and narrows down to the files most likely to contain the flaw. Cisco describes this as learned retrieval behavior rather than raw scale doing the work, a position the team traces back to earlier Foundation AI research showing that compact models can learn to search, reflect, and revise strategy on their own.
The output is a ranked list of files along with the terminal exploration trace that produced it, which gives reviewers something they can replay, question, and trust or reject.
The Vulnerability Localization Benchmark
General coding benchmarks measure general problem solving, not whether a model can localize vulnerable files from CWE-style descriptions. To fill that gap, Cisco introduced a 500-task benchmark that asks a model to navigate unfamiliar codebases while recognizing patterns tied to specific CWE categories. The closest adjacent reference is CodeScout, a terminal-based code-search agent described in the arXiv paper “CodeScout: An Effective Recipe for Reinforcement Learning of Code Search Agents” (arXiv:2603.17829, submitted March 18, 2026, by Lintang Sutawika and co-authors), which reports that its models match or beat LLMs 2 to 18 times larger on SWE-Bench Verified, Pro, and Lite. CodeScout evaluates software-engineering search, not security-driven localization, which is exactly the gap the new benchmark is built to address.
What to check on your own site
If you run technical SEO or application security audits, a tool like Antares slots in at the triage layer. Practical checks to consider adding to an audit checklist:
- Map known CWEs to specific files in the repository rather than treating the whole codebase as equally risky.
- Inspect the trace output, not just the file list, so you can see why a file was flagged.
- Compare the model’s shortlist against static analyzer results to find disagreements that deserve a closer look.
- Add a CI step that re-scans on every commit when working on plugins, themes, or internal admin tooling.
- Keep dependency and software composition analysis, secret scanning, dynamic testing, and human review in the loop. Antares does not replace them.
How Antares fits inside Cisco’s security AI work
Antares is the third piece in a connected effort. Foundry Security Spec gives a model-agnostic blueprint for agentic security evaluation, with defined roles, guardrails, and reviewable outputs. CodeGuard contributes secure-by-default rules that can steer AI coding agents toward safer code. Antares handles the localization step, turning vulnerability intelligence into a ranked list of files that humans can review. Together they form a loop: prevention rules shape the code an agent writes, and localization models help humans verify the code that ships.
Who is speaking to the work
Reza Shokri, Associate Professor of Computer Science at the National University of Singapore, said the model is small enough to navigate a codebase and surface security issues that would otherwise demand larger models or more manual work. Amin Saberi, Professor of Management Science and Engineering and Director of the Language, Data, and Reasoning Lab at Stanford University, framed the release in terms of access, noting that advanced AI-based detection has mostly belonged to organizations with frontier-scale budgets and that Antares changes that balance enough to make always-on scanning realistic for every team.
Where to get it
Antares-350M and Antares-1B are available on Hugging Face along with the model card. The accompanying technical paper covers methodology, and the Cisco Foundation AI team is the contact point for follow-up questions.
FAQ
What is Antares and when was it released?
Antares is a family of small language models from Cisco, announced on July 21, 2026, designed for vulnerability localization. The first two releases, Antares-350M and Antares-1B, are open-weight and hosted on Hugging Face, with Antares-3B described as coming soon.
Why does a small model matter for code security scanning?
The compact size keeps inference costs low and lets the models run locally, which means proprietary source code never has to be uploaded to an external cloud service. That makes always-on, per-commit security scanning practical for teams with limited budgets or strict privacy requirements.
What is the Vulnerability Localization Benchmark?
It is a 500-task benchmark released alongside Antares. Each task requires a model to navigate an unfamiliar codebase and identify files likely to contain vulnerabilities tied to specific CWE categories, a focus the Cisco team says general coding benchmarks and adjacent work like CodeScout do not directly address.