Urgent.News

What's breaking now, across thousands of outlets.

AI

Three AI Coding Agents, Three Ways to Break Them, and One Thing Detection Will Never Give You

Three AI Coding Agents, Three Ways to Break Them, and One Thing Detection Will Never Give You I've spent the last week reading through the technical writeups from Novee Security's Black Hat USA 2026 briefing, "Trusted Enough to Run: Breaking AI Agents in Official Workflows." The title sounds broad. The content is not. They found three distinct, exploitable vulnerabilities in three of the most…

Three AI coding agents have distinct vulnerabilities that highlight a critical issue in their design. The vulnerabilities exist within Claude Code, Gemini CLI, and OpenAI Codex, all of which are widely used tools. These flaws demonstrate that detection alone is insufficient to safeguard against AI agent exploitation. Each vulnerability stems from a trust handoff failure, where the agent's validator trusts that the input it receives is exactly what will execute.

This trust failure enables attackers to manipulate the agents by injecting malicious commands or environment variables, leading to potential supply chain compromises. The root cause lies in the architecture of these agents: they trust the sanitized representation of input, unaware that attackers can bypass this validation. The vulnerabilities expose the need for cryptographic evidence to prove what actually occurred after trust boundaries are crossed, as detection cannot ensure the integrity of the trust handoff.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

Spotting Invisible LLM Agent Bugs with Agnost AI

Detecting Invisible Errors in LLM‑Powered Agents with Agnost AI Your practical guide to monitoring, debugging, and automating remediation in production pipelines Introduction When your autonomous…

  • Agnost AI detects invisible LLM agent errors in production
  • Monitors runtime state, tool calls, latency, token usage
  • Identifies issues over weeks, unlike traditional testing

Upgrading Your Embedding Model Doesn't Break RAG Loudly — It Breaks It Quietly

The problem A team I was helping upgraded their embedding model to cut cost — swapped an older general-purpose embedding model for a newer, cheaper one.

  • Upgrading embedding model to cheaper one reduces costs without schema changes or errors.
  • Retrieval systems return most similar vectors even if incorrect, no errors thrown.
  • Mixing embedding models in one index silently corrupts retrieval results over time.

While AI Is Thinking

You wake up. Your brain isn’t quite awake yet, but social media already seems to be having a very productive morning. “Here’s what you can do with AI.” “If you don’t know this trick, you’re missing…

  • AI users report increased productivity with certain tricks
  • Uncertainty remains about effective AI usage and requests
  • Suggests using AI time for relaxation and unrelated thoughts

More from Wednesday 26 August →