What Is an AVE Record and Why CVE Does Not Work for AI Agents?

Reddit r/AI_Agents News

Summary

The article introduces the Agent Vulnerability Enumeration (AVE) record as a new standard designed to address the inadequacies of CVE for AI agent vulnerabilities, covering scoring, detection, and standardization challenges specific to agentic AI.

CVE was built for code vulnerabilities that have patches. Agentic AI vulnerabilities are behavioral patterns in natural language. No binary to patch. The attack surface is every sentence an agent reads. Why that required a new standard: 1/ The scoring problem: Same prompt injection attack in two contexts: Stateless chatbot, no tools: CVSS 4.0 Agent with persistent memory, tool access, multi-agent spawning: 8.5 CVSS captures neither the autonomy level nor the tool blast radius. AIVSS does. 10 Agentic Risk Amplification Factors, each 0.0/0.5/1.0. 2/ The detection problem: CVE records describe what happened after an exploit. They do not include behavioral fingerprints for static analysis. AVE records include: \- Behavioral IOCs \- Detection methodology \- Pattern examples \- OWASP MCP + ASI mapping \- Remediation 3/ The standard problem: "Tool poisoning" and "tool description injection" are the same attack. Without stable IDs, you cannot write detection rules that share a taxonomy. AVE gives every attack class a stable ID, 48 records. Apache 2.0. Open for contributions.
Original Article

Similar Articles

AEVS

Product Hunt

AEVS is a proof-of-execution tool for AI agents, launched on ProductHunt by Fetch.ai.

AVE-Compass: Towards Holistic Evaluation for Audio-Video Editing Abilities

Hugging Face Daily Papers

AVE-Compass is a new benchmark for holistic evaluation of audio-video editing abilities, with 145 videos, 196 editing instructions, and 2,688 checklist items. It also proposes AVE-Agent, a modular agent framework that improves cross-modal editing via self-reflection and evaluator feedback.