{
  "id": 20265203,
  "title": "Fixing a Cross-Tenant Approval Isolation Gap in RagLeap Agents 0.5.1",
  "url": "https://urgent.news/2026/11/16/fixing-a-cross-tenant-approval-isolation-gap-in-ragleap-agents-0-5-1",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-16T05:28:34.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/ragleap/fixing-a-cross-tenant-approval-isolation-gap-in-ragleap-agents-051-32fe"
  },
  "original_language": "en",
  "account": "RagLeap Agents 0.5.1 addresses a security concern where one tenant could resume another tenant's paused AI agent run. This vulnerability was discovered in RagLeap Agents 0.5.0. The fix involves binding run() and resume() operations to a tenant scope, implemented in the new scope-aware APIs. The scope is stored with the run, and resume requests must match this scope. If a request is from the wrong tenant or the run ID is unknown, the system returns the same error: ResumeError (unknown run). This prevents exposing whether a run exists under a different tenant.\n\nAdditional security enhancements include stronger run IDs, 22-character URL-safe tokens with 128 bits of randomness, mandatory scope mode where applications can enforce scope enforcement, audit logging, per-scope rate limiting, and sub-agent scope inheritance. These improvements are part of the ragleap-security =0.2.0 package, which uses the Python standard library.\n\nTesting involved verifying the test suite, GitHub CI, mutation tests in Python 3.12.3 and 3.10.20, published wheel source comparison, and cross-tenant resume verification using the published wheel. The release did not guarantee that scope enforcement is a complete authentication system, and the application must still authenticate users and pass the correct scope. The in-memory rate limiter does not retain state across restarts. The testing also did not cover Windows, macOS, real model-provider execution, and network filesystems.\n\nWhile RagLeap Agents 0.5.1 makes boundaries explicit and adds regression coverage for the reproduced issue, it is not a complete authentication system and does not ensure stronger separation of shared state stores. Developers and security practitioners are encouraged to inspect, test, and contribute to the open-source RagLeap Agents 0.5.1.",
  "summary": "Fixing a Cross-Tenant Approval Isolation Gap in RagLeap Agents 0.5.1 What happens when one tenant can resume another tenant's paused AI agent run? We reproduced that scenario in RagLeap Agents 0.5.0. The result was a security improvement focused on scope-bound execution and approval isolation, released as RagLeap Agents 0.5.1 . The vulnerability scenario Consider a shared agent instance and state…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}