CVE-2026-33010

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 95% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

mcp-memory-service is an open-source memory backend for multi-agent systems. Prior to version 10.25.1, when the HTTP server is enabled (MCP_HTTP_ENABLED=true), the application configures FastAPI's CORSMiddleware with allow_origins=['*'], allow_credentials=True, allow_methods=["*"], and allow_headers=["*"]. The wildcard Access-Control-Allow-Origin: * header permits any website to read API responses cross-origin. When combined with anonymous access (MCP_ALLOW_ANONYMOUS_ACCESS=true) - the simplest way to get the HTTP dashboard working without OAuth - no credentials are needed, so any malicious website can silently read, modify, and delete all stored memories. This issue has been patched in version 10.25.1.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
31.0%
KEV
Not listed

Published

March 20, 2026

Last Modified

April 14, 2026

References (2)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
mcp-memory-service10.0.0 ... 9.3.1 (187 versions)10.25.1—

Data Freshness Timeline

(refreshed 12× in last 7d / 43× 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.

  1. 2026-07-17 07:46 UTCOSV refresh
  2. 2026-07-16 17:03 UTCEPSS rescore
  3. 2026-07-16 17:03 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 16:57 UTCEPSS rescore
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-13 22:30 UTCEPSS rescore
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-13 06:13 UTCEPSS rescore
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-08 15:15 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-01 15:06 UTCEPSS rescore
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-29 05:32 UTCOSV refresh
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 14:07 UTCEPSS rescore
Show 68 more
  1. 2026-06-28 04:56 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-27 03:08 UTCEPSS rescore
  4. 2026-06-25 13:49 UTCEPSS rescore
  5. 2026-06-25 13:49 UTCEPSS rescore
  6. 2026-06-24 14:05 UTCEPSS rescore
  7. 2026-06-23 21:33 UTCEPSS rescore
  8. 2026-06-23 21:33 UTCEPSS rescore
  9. 2026-06-22 14:25 UTCEPSS rescore
  10. 2026-06-22 14:25 UTCEPSS rescore
  11. 2026-06-21 14:56 UTCEPSS rescore
  12. 2026-06-21 14:56 UTCEPSS rescore
  13. 2026-06-21 01:59 UTCEPSS rescore
  14. 2026-06-19 19:25 UTCEPSS rescore
  15. 2026-06-19 19:25 UTCEPSS rescore
  16. 2026-06-18 17:52 UTCEPSS rescore
  17. 2026-06-18 17:52 UTCEPSS rescore
  18. 2026-06-17 17:53 UTCEPSS rescore
  19. 2026-06-16 17:52 UTCEPSS rescore
  20. 2026-06-15 17:49 UTCEPSS rescore
  21. 2026-06-14 23:18 UTCEPSS rescore
  22. 2026-06-13 23:00 UTCEPSS rescore
  23. 2026-06-12 23:12 UTCEPSS rescore
  24. 2026-06-12 23:12 UTCEPSS rescore
  25. 2026-06-11 14:00 UTCEPSS rescore
  26. 2026-06-10 22:18 UTCEPSS rescore
  27. 2026-06-10 13:22 UTCEPSS rescore
  28. 2026-06-08 14:17 UTCEPSS rescore
  29. 2026-06-08 14:17 UTCEPSS rescore
  30. 2026-06-07 15:25 UTCEPSS rescore
  31. 2026-06-07 15:25 UTCEPSS rescore
  32. 2026-06-07 15:25 UTCEPSS rescore
  33. 2026-06-06 13:47 UTCEPSS rescore
  34. 2026-06-06 13:47 UTCEPSS rescore
  35. 2026-06-05 22:47 UTCEPSS rescore
  36. 2026-06-05 22:47 UTCEPSS rescore
  37. 2026-06-05 06:10 UTCEPSS rescore
  38. 2026-06-05 06:10 UTCEPSS rescore
  39. 2026-06-04 13:12 UTCEPSS rescore
  40. 2026-06-04 13:12 UTCEPSS rescore
  41. 2026-06-02 20:13 UTCEPSS rescore
  42. 2026-06-01 13:52 UTCEPSS rescore
  43. 2026-06-01 13:52 UTCEPSS rescore
  44. 2026-06-01 13:51 UTCEPSS rescore
  45. 2026-06-01 08:13 UTCOSV refresh
  46. 2026-05-31 22:30 UTCEPSS rescore
  47. 2026-05-31 22:30 UTCEPSS rescore
  48. 2026-05-31 00:16 UTCEPSS rescore
  49. 2026-05-31 00:16 UTCEPSS rescore
  50. 2026-05-31 00:16 UTCEPSS rescore
  51. 2026-05-29 13:44 UTCEPSS rescore
  52. 2026-05-29 13:44 UTCEPSS rescore
  53. 2026-05-28 13:44 UTCEPSS rescore
  54. 2026-05-28 13:44 UTCEPSS rescore
  55. 2026-05-28 13:44 UTCEPSS rescore
  56. 2026-05-27 13:40 UTCEPSS rescore
  57. 2026-05-27 13:40 UTCEPSS rescore
  58. 2026-05-27 13:40 UTCEPSS rescore
  59. 2026-05-26 13:44 UTCEPSS rescore
  60. 2026-05-26 07:18 UTCEPSS rescore
  61. 2026-05-26 07:18 UTCEPSS rescore
  62. 2026-05-20 22:38 UTCEPSS rescore
  63. 2026-05-20 22:38 UTCEPSS rescore
  64. 2026-05-20 20:51 UTCEG score recompute
  65. 2026-05-20 11:22 UTCEPSS rescore
  66. 2026-05-20 11:22 UTCEPSS rescore
  67. 2026-05-20 11:21 UTCEPSS rescore
  68. 2026-05-18 21:31 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-33010?
CVE-2026-33010 is a high vulnerability published on March 20, 2026. mcp-memory-service is an open-source memory backend for multi-agent systems. Prior to version 10.25.1, when the HTTP server is enabled (MCPHTTPENABLED=true), the application configures FastAPI's CORSMiddleware with alloworigins=['*'], allowcredentials=True, allowmethods=["*"], and…
When was CVE-2026-33010 disclosed?
CVE-2026-33010 was first published in the National Vulnerability Database on March 20, 2026, with the most recent update on April 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33010 actively exploited?
CVE-2026-33010 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-33010?
CVE-2026-33010 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-33010?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33010, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33010

Explore →

Is Your Infrastructure Affected by CVE-2026-33010?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs