What is the CVSS score of CVE-2026-33010?

CVE-2026-33010 has a CVSS 3.1 base score of 8.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

Which versions of Cors Misconfiguration are affected by CVE-2026-33010?

mcp-memory-service instances with HTTP APIs exposed to the internet face a high-risk CORS misconfiguration that allows unauthenticated attackers from any website to read, modify, and delete stored…. A patch is available.

How to fix or mitigate CVE-2026-33010?

Within 24 hours: Inventory all mcp-memory-service deployments, identify instances with HTTP APIs exposed and anonymous access enabled, and immediately disable the HTTP interface or restrict network access to trusted internal networks only. Within 7 days: Implement WAF rules to block cross-origin requests or require strict CORS headers; disable anonymous access in all remaining instances. Within 30 days: Upgrade to version 10.25.1 or later once available, or migrate to alternative solutions if patching is unavailable; conduct audit of memory data for unauthorized access or modification during the vulnerability window.

Cors Misconfiguration CVE-2026-33010

EUVD-2026-13766 HIGH

Permissive Cross-domain Security Policy with Untrusted Domains (CWE-942)

2026-03-20 GitHub_M

GHSA-g9rg-8vq5-mpwm

Cors Misconfiguration Information Disclosure

8.1

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

8.1 HIGH

AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

EUVD ID Assigned

Mar 20, 2026 - 18:46 euvd

EUVD-2026-13766

Analysis Generated

Mar 20, 2026 - 18:46 vuln.today

CVE Published

Mar 20, 2026 - 18:33 nvd

HIGH 8.1

DescriptionGitHub Advisory

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.

AnalysisAI

A CORS misconfiguration vulnerability in mcp-memory-service allows any malicious website to perform cross-origin requests to the HTTP API. Versions prior to 10.25.1 of mcp-memory-service from doobidoo are affected, particularly when the HTTP server is enabled with anonymous access, allowing attackers to read, modify, and delete all stored memories without authentication. No KEV listing or public exploitation indicators are currently reported, though the vulnerability's simplicity and the availability of a GitHub security advisory suggest proof-of-concept development would be straightforward.

Technical ContextAI

The vulnerability affects mcp-memory-service (CPE: cpe:2.3:a:doobidoo:mcp-memory-service:*:*:*:*:*:*:*:*), an open-source memory backend for multi-agent systems. The root cause is CWE-942 (Permissive Cross-domain Policy with Untrusted Domains), where the FastAPI application configures CORSMiddleware with wildcard origins (allow_origins=['*']) combined with allow_credentials=True. This violates the CORS security model, as browsers should not honor credentials with wildcard origins, but the misconfiguration becomes critical when paired with anonymous access mode (MCP_ALLOW_ANONYMOUS_ACCESS=true). The FastAPI framework's CORS middleware allows all HTTP methods and headers, effectively removing cross-origin security boundaries entirely when the HTTP dashboard is enabled via MCP_HTTP_ENABLED=true.

RemediationAI

Upgrade mcp-memory-service to version 10.25.1 or later, which patches the CORS misconfiguration as documented in the GitHub security advisory at https://github.com/doobidoo/mcp-memory-service/security/advisories/GHSA-g9rg-8vq5-mpwm. As immediate workarounds prior to patching, disable the HTTP server by setting MCP_HTTP_ENABLED=false if the dashboard is not required, or implement authentication by disabling anonymous access (set MCP_ALLOW_ANONYMOUS_ACCESS=false) and configuring OAuth properly. Deploy a reverse proxy with strict CORS policies that whitelist only trusted domains, and implement network-level access controls to restrict the service to trusted IP ranges. Review and rotate any sensitive data stored in the memory service, as previous exposure cannot be ruled out for vulnerable deployments.