> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flintai.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Unauthenticated agent communication

> Messages between agents carry no cryptographic identity proof — any party can spoof an agent

Messages between agents carry no cryptographic identity proof — any party can spoof an agent

## How to resolve

Require mutual authentication (mTLS, signed tokens) for all agent-to-agent communication. Verify sender identity before processing messages.

## Risk

**Governance/Compliance**

This vulnerability falls under [ASI07:2026 — Insecure Inter-Agent Communication](https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/) in the OWASP Top 10 for Agentic Applications. Agent-to-agent messages lack authentication, encryption, or semantic validation.

**Security**

Messages between agents carry no cryptographic identity proof — any party can spoof an agent. If exploited, this can compromise the agent's integrity, confidentiality, or availability, potentially affecting downstream systems and data.

## Explanation

Messages between agents carry no cryptographic identity proof — any party can spoof an agent. This falls under ASI07 (Insecure Inter-Agent Communication): Agent-to-agent messages lack authentication, encryption, or semantic validation.

## Specifications

**Trigger**

* Agent scan detects messages between agents carry no cryptographic identity proof — any party can spoof an agent

The scanner looks for patterns such as:

* agent communication with no sender authentication
* GroupChat with no speaker verification
* agent messages trusted implicitly by role name

**Severity**

* HIGH

**Applies to**: Agent