<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AISVS on Joe Bollen Security</title><link>https://joe-b-security.github.io/tags/aisvs/</link><description>Recent content in AISVS on Joe Bollen Security</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Yes, it's a real three-body problem simulation</copyright><lastBuildDate>Sun, 05 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://joe-b-security.github.io/tags/aisvs/index.xml" rel="self" type="application/rss+xml"/><item><title>TOCTOU Race Conditions in Multi-Agent Systems</title><link>https://joe-b-security.github.io/posts/2026-04-05-toctou-agents/</link><pubDate>Sun, 05 Apr 2026 00:00:00 +0000</pubDate><guid>https://joe-b-security.github.io/posts/2026-04-05-toctou-agents/</guid><description>&lt;p&gt;Agent systems that do useful work tend to have multiple agents running concurrently, often reading and writing to the same underlying state. A support agent handles incoming requests while an ops agent processes escalations against the same ticket database, or a compliance agent monitors for policy violations on the same access control list that an access management agent writes grants to. When these agents run concurrently and their operations interleave, the same timing vulnerabilities that have existed in operating systems and concurrent programming for decades show up again.&lt;/p&gt;</description></item></channel></rss>