Authorization Bypass Through User-Controlled Key Affecting aegra-api package, versions [0.9.0,0.9.7)


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.04% (12th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Authorization Bypass Through User-Controlled Key vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-PYTHON-AEGRAAPI-16635359
  • published11 May 2026
  • disclosed7 May 2026
  • creditvictorjmarin

Introduced: 7 May 2026

NewCVE-2026-44504  (opens in a new tab)
CWE-285  (opens in a new tab)
CWE-639  (opens in a new tab)

How to fix?

Upgrade aegra-api to version 0.9.7 or higher.

Overview

aegra-api is an Aegra core API - Self-hosted Agent Protocol server

Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key in the POST /threads/{thread_id}/runs, POST /threads/{thread_id}/runs/stream, and POST /threads/{thread_id}/runs/wait endpoints when thread ownership is not properly verified against the authenticated user. An attacker can gain unauthorized access to another user's thread data, execute actions on behalf of other users, and read or inject messages into another user's conversation history by supplying a valid thread_id belonging to a different user. This is only exploitable if the deployment has multiple authenticated users on a shared instance and no custom authorization handler is registered for thread run creation.

Workaround

This vulnerability can be mitigated by registering an @auth.on("threads", "create_run") handler that explicitly verifies thread ownership against the authenticated identity before allowing the operation.

CVSS Base Scores

version 4.0
version 3.1