# CVE-2026-38924: Misconfiguration in Serena

> The MCP server binds to all network interfaces by default, exposing the service to unauthorized network access.

- **Severity:** Low 2.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-gx4x-gc82-v87q, GHSA-m922-r24v-6wff

## What is CVE-2026-38924?

CVE-2026-38924 is a low-severity vulnerability in Oraios AI Serena, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Oraios AI Serena before 1.0.0, the listen address of the MCP server in HTTP mode is 0.0.0.0. NOTE: the Supplier observed that 0.0.0.0 was a "potential security hazard" but the Serena documentation, at the time of the issue report proposing 127.0.0.1 instead of 0.0.0.0, recommended "use a sandboxed environment for running Serena."

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

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


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

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

## Is CVE-2026-38924 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-38924 is a low-severity vulnerability in Oraios AI Serena, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-38924 exists.

Affected product: Oraios AI Serena. 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-38924/ (Markdown: https://insights.sbomify.com/CVE-2026-38924/index.md)
```

## Sources

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

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