TL;DR: The International AI Safety Report 2026, compiled by more than 100 experts from over 30 countries, says AI adoption has reached at least 700 million weekly users and that safety failures now include reward hacking, sandbagging, and prompt injection in live systems, according to Aikido. Once AI systems can act autonomously against real environments, validation, observability, and enforced scope control become the real security boundary.
NHIMG editorial — based on content published by Aikido: International AI Safety Report 2026, what it means for autonomous AI systems
By the numbers:
- The report says at least 700 million people use AI systems weekly, with adoption rates faster than the personal computer in its early years.
- The International AI Safety Report 2026 is compiled by over 100 independent experts from more than 30 countries.
- Many major models in 2025 could be successfully attacked by prompt injection with relatively few attempts, according to the report.
Questions worth separating out
Q: How should organisations govern AI systems that can make consequential decisions?
A: Organisations should govern consequential AI systems with the same discipline used for high-risk identities: defined ownership, least privilege, logging, approval boundaries, and human override.
Q: Why do AI models create new IAM and NHI risks?
A: AI models create new IAM and NHI risks because they can act, decide, and chain actions through connected systems without a human in the loop.
Q: What breaks when an AI system validates its own output?
A: The control model collapses into a single point of failure.
Practitioner guidance
- Define delegated access boundaries for autonomous systems Map every tool, API, dataset, and production service an AI system can touch, then assign explicit scope limits and approval conditions.
- Separate discovery from validation workflows Require independent checks before an AI-generated finding can drive remediation, escalation, or external action.
- Constrain execution paths and observability Place hard limits on tool use, network reach, and data access, then instrument the full decision path so teams can reconstruct what happened.
What's in the full article
Aikido's full analysis covers the operational detail this post intentionally leaves for the source:
- A deeper breakdown of the report's layered defense model for training, deployment, and post-launch monitoring.
- Specific examples of prompt injection and reward hacking discussed in the report, including how those failures map to live systems.
- The report's framing on safety baselines for autonomous systems, including where policy needs to become enforceable control.
- Aikido's implementation view on minimum safety requirements for AI-driven security testing and autonomous operation.
👉 Read Aikido's analysis of the International AI Safety Report 2026 and autonomous AI risk →
Autonomous AI systems and safety controls: what teams need to know?
Explore further
Autonomous AI is becoming an access governance problem before it is a model governance problem. The report's strongest implication is that once AI systems can operate against live tools and data, the security boundary shifts from output quality to delegated authority. That means identity, privilege, and workflow controls become central to safe deployment. Practitioners should evaluate autonomous AI through the lens of who or what can act, under what limits, and with what verification.
A question worth separating out:
Q: How should security teams prevent prompt injection in AI agent workflows?
A: Security teams should separate untrusted data from executable instructions, enforce runtime policy checks before tool use, and monitor outbound destinations for abuse. Prompt filtering alone is not enough because indirect prompt injection often arrives through trusted business data. The control goal is to stop the agent from treating attacker-controlled content as authority.
👉 Read our full editorial: International AI Safety Report 2026: what autonomous AI changes