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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 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
- 31 Oct 2026, 15:02 UTC First seen by agentprime
- 31 Oct 2026, 15:02 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-m98r-6667-4wq7
- OSV: GHSA-m98r-6667-4wq7
- github.com/aegra/aegra/security/advisories/GHSA-m98r-6667-4wq7
- nvd.nist.gov/vuln/detail/CVE-2026-44504
- github.com/aegra/aegra/issues/336
- github.com/aegra/aegra/pull/337
- github.com/aegra/aegra/commit/e1b2042254fd49072ca281bc35b3f2a3bed74b31
- github.com/aegra/aegra
- github.com/aegra/aegra/releases/tag/v0.9.7