Skip to content

AAK-A2A-012: A2A schema confusion between major versions

Severity
MEDIUM
Category
A2A Protocol (a2a-protocol)
Scanner
agent_audit_kit/scanners/a2a_protocol.py
Auto-fixable
No.
SARIF name
A2aSchemaConfusion

What it detects

An A2A endpoint accepts messages without version discriminator, allowing a v1 payload to be interpreted by a v2 handler (or vice versa) with changed field semantics. Schema confusion is a message-semantics gap of the kind OWASP ASI07 (Insecure Inter-Agent Communication) names.

How to fix

Add a schema_version (or a2a_version or apiVersion) field to the Agent Card, and have the agent reject messages whose version does not match. The rule asks for it on cards that carry a tokens, delegation or trust section.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-A2A-012

Limitations

Asks for a schema_version, a2a_version or apiVersion only from a card that has a tokens, delegation or trust block, and only checks that the key exists: a card with none of those blocks, or with "schema_version": "", is not reported.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-A2A-012.md: the page then shows that text, with the registry reference appended under it.