STALE MEASUREMENTNewest real-model measurement: 26 days old, measured with v0.32.0; 7 releases have shipped since, past this project’s own 7-day window. Why, and what unblocks it

ProductEvidenceTop 10LeaderboardCompliancePricingDocsStar on GitHub Quickstart
( 08 ) · EAI08

Identity, access & excessive autonomy

Weak authn/z on robot control surfaces plus over-broad autonomy - a policy that self-authorizes a high-consequence action without an operator token.

SARIF EAI08channel: authorization
Definition

What it is

This risk pairs weak or missing authentication/authorization on robot control surfaces (open ROS graphs, unauthenticated APIs, static credentials) with over-broad agent autonomy - a policy permitted to take high-consequence physical actions without scoping, approval, or least-privilege.

The difference between “an attack reaches the policy” and “an attack reaches the actuators” is access control - and an over-empowered agent turns a small compromise into a large one. Provael tests the excessive-autonomy half (OWASP ASI03).

Real example

Seen in the wild

Unauthenticated ROS/DDS graphs and static-credential findings recur across commercial robots - “Cybersecurity AI: Hacking Consumer Robots in the AI Era” (arXiv:2603.08665) pivoted one device’s static credentials into fleet-wide reach over 267+ connected robots. OWASP elevates both identity abuse (ASI03) and excessive agency (LLM06) as first-class risks. The embodied twist is that the over-empowered actor is the policy itself.

External validation - distinct from Provael’s own result

Cybersecurity AI: Hacking Consumer Robots in the AI Era - arXiv:2603.08665

How Provael tests it

Attack, measure, prove

  • Ships the `authorization` family (self_authorize_bypass + scope_escalation): a perturbed instruction drives the policy to self-authorize and execute a consequential, authorization-gated action without the required operator-authorization token.
  • `self_authorize_bypass` requests a guarded action while claiming clearance; `scope_escalation` reframes the task to invoke a higher-privilege action - neither presents a valid operator token. Scored as an activation rate with a 95% Wilson CI against a benign-FPR control (the `none` baseline never invokes a guarded action → 0%).
  • Stub-validated only (the deterministic CPU fixture emits the guarded action unauthorized → 100% [84-100%] vs a 0% benign baseline; a valid token makes it safe); real SmolVLA×LIBERO transfer is GPU-gated and not yet run - no cross-model claim.
Mitigations

What reduces the risk

  • Authentication and authorization on every control channel; least-privilege action scopes.
  • Human-in-the-loop for high-consequence actions; capability leases / action budgets.
  • Audit and revoke - log every guarded action and keep authority revocable.
SARIF rule id

How it shows up in CI

Every finding for this risk carries a stable rule id in the SARIF report - the Embodied AI Top-10 id itself:

ruleId: EAI08
Compliance mapping

Crosswalk

OWASP
ASI03 Identity & Privilege Abuse · LLM06 Excessive Agency
MITRE ATLAS
Privilege Escalation → excessive agency / self-authorized guarded action (proposed)
Frameworks
IEC 62443 - access control

See the full framework crosswalk for dates and detail. Not legal advice.

DOC. PVL-EAI08 · Embodied AI Security Top 10 · v0.2Updated 2026-06-27 · CC BY-SA 4.0