Urgent.News

What's breaking now, across thousands of outlets.

Tech

Fixing a Cross-Tenant Approval Isolation Gap in RagLeap Agents 0.5.1

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…

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.

Additional 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.

Testing 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.

While 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.

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

How to Remove Duplicate Lines from a List (Free, Keeps Order, No Uploads)

Merged two email lists and now half the addresses appear twice. Exported keywords from three tools and the same terms repeat on every page.

  • Remove duplicates while preserving original order
  • Define duplicate criteria: exact match, case-insensitive, whitespace
  • Use free tool BulkTextKit for basic deduplication needs

How eSIM Provisioning Actually Works: QR Codes, SM-DP+ and the eUICC Explained

If you've ever bought a travel eSIM, you scanned a QR code and a few seconds later your phone had a new mobile line. But what actually happens in those seconds?

  • eSIM technology uses eUICC to store multiple profiles.
  • QR code scan initiates profile download via SM-DP+.
  • eSIM beneficial for travelers with multiple local-rate plans.

More from Monday 16 November →