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."
CVE-2026-38924
Score 2.9 from GitHub Security Advisory (severity: LOW) published 2026-09-14. a secondary CVSS source baseline 2.9; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.9
- EG Score
- 2.9(high)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity29% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- KEV
- Not listed
Published
September 14, 2026
Last Modified
September 14, 2026
References (6)
- cve@mitrehttps://dash.security/blog/cve-2026-38924-unauthenticated-rce-in-the-serena-mcp-server
- cve@mitrehttps://github.com/oraios/serena/commit/a7af5c1f8a9ea27102eac9e72f64dd97dbfefff3
- cve@mitrehttps://github.com/oraios/serena/commit/b00ae292ac2d49947506886f44eb1cad7b7d7cd1
- cve@mitrehttps://github.com/oraios/serena/compare/v0.1.4...v1.0.0
- cve@mitrehttps://github.com/oraios/serena/security/advisories/GHSA-m922-r24v-6wff
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://dash.security/blog/cve-2026-38924-unauthenticated-rce-in-the-serena-mcp-server
Vendor Advisories for CVE-2026-38924(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 15× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 20:31 UTCEG score recompute
- 2026-09-17 20:31 UTCGHSA enrichment
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-14 17:27 UTCEG score recompute
- 2026-09-14 17:27 UTCGHSA enrichment
- 2026-09-14 16:45 UTCEG score recompute
- 2026-09-14 16:45 UTCGHSA enrichment
- 2026-09-14 03:20 UTCEG score recompute▲ 2.90
- 2026-09-14 03:20 UTCNVD updateCVSS v3 → 2.9 · severity → LOW
- 2026-09-14 02:55 UTCEG score recompute
- 2026-09-14 02:54 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-38924?
When was CVE-2026-38924 disclosed?
Is CVE-2026-38924 actively exploited?
What is the CVSS score of CVE-2026-38924?
How do I remediate CVE-2026-38924?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-38924
Is Your Infrastructure Affected by CVE-2026-38924?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.