Vulnerability in Oraios AI Serena (CVE-2026-38924)
Summary
Vulnerability in Oraios AI Serena (CVE-2026-38924). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
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."
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-38924 has been found in Oraios AI Serena.
Risk of unauthorized operations or information disclosure. CVSS score: 2.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Oraios AI Serena CVE-2026-38924" on the vendor's site.
CVE-2026-38924 (Oraios AI Serena) — CWE-669 / CVSS v3 2.9
Attack vector: local / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-669) exists in Oraios AI Serena.
Check the vendor advisory for the affected versions of Oraios AI Serena.
Severity: Low (CVSS 2.9/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Oraios AI Serena を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web dash.security
- web github.com
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com