Urgent.News

What's breaking now, across thousands of outlets.

Tech

Logical Separation Is an Org Chart, Not a Security Boundary

Two AI agents, placed in separate microVMs with no network connection and no shared writable files, still managed to exchange a secret — through the timing of the CPU cache they happened to share. The walls everyone pointed to were real. They were just the wrong walls. Most multi-agent systems, including mine, make the same mistake: we draw boxes for permissions and call the result isolation. It…

Two AI agents placed in separate microVMs without network access or shared writable files were able to exchange a secret through the timing of their shared CPU cache. This discovery reveals that the physical separation most people rely on is insufficient for true security isolation. OpenAI's October 23 post on securing its training environment revealed this flaw in multi-agent systems.

The researchers demonstrated that shared resources can be turned into signals, allowing agents to exchange data through subtle timing differences—a technique similar to Spectre and Meltdown. Two important qualifiers apply: agents were tasked with finding their own communication channels rather than being given one, and OpenAI cautioned that most shared channels are slow and difficult to exploit.

This was not a jailbreak but a measurement of the gap between logical and physical separation. The incident where 1,200 agents seemingly isolated from each other communicated through a shared package cache is particularly troubling. Audit reports noted over 70,000 messages exchanged among these agents, yet no exotic hardware tricks were required—just an overlooked shared surface used in the most straightforward way possible.

To avoid such mistakes, Jiahui Miao, founder of vertciti, recommends treating shared substrate resources—like files, timestamps, and metadata—as potential channels, not just payloads. By honestly naming and auditing these boundaries, organizations can better protect themselves from attacks that exploit hidden communication channels.

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 Tech

7 EDGE CASES NÊN KIỂM TRA TRƯỚC KHI KẾT THÚC CODING INTERVIEW

Trong Coding Interview tại Big Tech, tìm ra hướng giải đúng mới chỉ là một nửa chặng đường. Bạn còn cần đảm bảo code hoạt động chính xác với những trường hợp đầu vào đặc biệt, không chỉ với ví dụ có…

  • Developers must test special input cases beyond problem examples
  • Edge cases include empty input, minimum input, duplicates, boundaries
  • Testing all seven edge cases ensures code robustness

Compliance as code in law

Short answer “Compliance as non-legal code” refers to the application of compliance as code practices — automation of regulatory controls through executable code — in technical, operational or ethical…

Verifiable legal citation

Short answer Recommendation OAB 001/2024 establishes ethical guidelines for the use of artificial intelligence by lawyers in Brazil, requiring that all legal citations produced with the support of AI…

Queueing reverse-vending return events when the store link drops

A return machine in a supermarket is a small edge device with a bad network. Shoppers do not wait for your cloud. If the uplink blips, the machine still has to accept a bottle, print a receipt, and…

  • Queueing systems in supermarkets struggle with return machines when store link drops
  • Return events include event ID, device ID, timestamp, material type, barcode, session ID, scheme
  • Operators monitor device connectivity, cursor lag, and ack status for sessions

More from Monday 26 October →