dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-44504

HIGH · 8.6 CVSS v4.0 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Aegra is a drop-in replacement for LangSmith Deployments. Prior to 0.9.7, with multiple authenticated users on a shared instance are vulnerable to a cross-tenant IDOR. Any authenticated attacker, given another user's thread_id, can execute graph runs against the user's thread, read the user's full checkpoint state, and inject arbitrary messages into the user's conversation history. This vulnerability is fixed in 0.9.7.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Aegra versions before 0.9.7 contain a cross-tenant Insecure Direct Object Reference (IDOR) vulnerability. Authenticated attackers on a shared multi-tenant instance can access, read, and modify other users' threads by leveraging known thread_ids, enabling unauthorized execution of graph runs, reading checkpoint states, and injecting arbitrary messages into other users' conversation history.

MitigationUpgrade to Aegra version 0.9.7 or later to obtain the security fix. Additionally, review and enforce proper tenant isolation and authorization checks for all thread-related API endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Aegra version
    Run 'aegra --version' or check the package manifest/version file in the installation directory to determine the exact version number installed
    Affected if The installed version is before 0.9.7 (e.g., 0.9.6, 0.9.5, etc.)
  2. Confirm multi-tenant deployment
    Review the deployment configuration or environment variables to determine whether this is a shared multi-tenant instance versus a single-tenant installation
    Affected if The environment is configured as a shared multi-tenant instance where multiple tenants share the same database and application server
  3. Inspect thread API endpoint authorization
    Review the source code or API configuration for thread-related endpoints (e.g., /api/threads, /api/threads/{thread_id}) to verify that tenant isolation and ownership validation are enforced on each request
    Affected if Thread API endpoints do not validate that the requesting user owns the thread_id or belong to the same tenant as the thread
  4. Verify thread_id access controls
    Test accessing thread endpoints with known thread_ids from different users/tenants using API calls or a test script to confirm unauthorized access is blocked
    Affected if Requests with a thread_id belonging to another user/tenant return successful responses instead of 403/404 errors

You are affected if running Aegra version 0.9.7 or earlier on a multi-tenant deployment where thread API endpoints lack proper tenant isolation and ownership validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Aegra version 0.9.7 or later to obtain the security fix. Additionally, review and enforce proper tenant isolation and authorization checks for all thread-related API endpoints.

Recommended fix High confidence

0.9.7

  1. Check the currently installed version of Aegra (e.g., pip show aegra or check package.json)
  2. Backup all existing data, configuration files, and database state
  3. Upgrade to version 0.9.7 using the appropriate package manager (e.g., pip install aegra==0.9.7 or npm install [email protected])
  4. Restart all Aegra services to load the updated version
  5. Verify the upgrade was successful by checking the installed version matches 0.9.7
  6. If applicable, run any provided migration scripts or tests to ensure the upgrade is functional

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44504 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44504 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data