Advisory record · GHSA-m98r-6667-4wq7

Aegra has cross-user run injection in /threads/{thread_id}/runs (IDOR)

CVSS 8.6 HighEPSS 0.0029 · 21st percentile

Published by the GitHub Advisory Database at 7 May 2026, 01:49 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
aegra-apiPyPI>=0.9.0, <0.9.70.9.7
Identifiers
GHSA-m98r-6667-4wq7 · CVE-2026-44504 · PYSEC-2026-2328
Weakness (CWE)
CWE-285 · CWE-639
Published
7 May 2026
Updated
13 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Aegra (aegra-api) versions 0.9.0 through 0.9.6 let any authenticated user on a shared instance run graphs against another user's thread if they know its thread ID, when no custom authorization handler is registered. The attacker can read the other user's checkpoint state from the run output, inject messages into that conversation, and hide the activity from the victim's run list. Upgrade to aegra-api 0.9.7, which adds an ownership check; until then, register an authorization handler for the create_run action that verifies thread ownership.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.6 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0029, the 21st percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:02 UTC First seen by agentprime
  2. 31 Oct 2026, 15:02 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.