# CVE-2026-124587: elizaOS eliza HTTP Server api-base-owner.ts information disclosure


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-mcvf-9h7r-2jgr

## What is CVE-2026-124587?

CVE-2026-124587 is a medium-severity vulnerability in elizaOS eliza, published on 9 Nov 2026. 

### Official description

A vulnerability was identified in elizaOS eliza 2.0.3-beta.7. The affected element is an unknown function of the file packages/app/platforms/electrobun/src/lifecycle/api-base-owner.ts of the component HTTP Server. Such manipulation leads to information disclosure. It is possible to launch the attack remotely. The exploit is publicly available and might be used. The name of the patch is cf6fa193017e70884e01c5bb7890f74b6b2b79d2. A patch should be applied to remediate this issue.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-124587?


## How do I fix CVE-2026-124587?

No fix has been published for CVE-2026-124587 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-124587 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124587 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124587 and fix it if it is affected.

What it is: CVE-2026-124587 is a medium-severity vulnerability in elizaOS eliza, published on 9 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124587 exists.

Affected product: elizaOS eliza. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-124587/ (Markdown: https://insights.sbomify.com/CVE-2026-124587/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-124587
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-124587
- OSV: https://osv.dev/vulnerability/CVE-2026-124587

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-124587/
Summaries are generated and may contain mistakes; the official description above is the record.