CVE-2026-53710

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 44% 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, secondary
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 10.0Exploit: None knownExposed: 0

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

MCP Context Forge is an AI gateway, registry, and proxy for MCP, A2A, REST, and gRPC APIs. Prior to 1.0.2, the python_sandbox_server in mcp-servers/python/python_sandbox_server/src/python_sandbox_server/server_fastmcp.py exposes raw getattr through safe_builtins, omits a required _getattr_ guard, and relies on validate_code checks for literal dangerous dunder strings. An attacker can construct dunder names at runtime, traverse the Python class hierarchy, reach subprocess.Popen, and execute OS commands with the server process privileges through the execute_code MCP tool. The HTTP/SSE transport can expose this tool without authentication, while stdio-only deployments have reduced network reachability. The issue affects the python_sandbox_server subproject and does not directly affect the core Context Forge gateway or proxy components. This issue is fixed in version 1.0.2.

CVSS v3
10.0
EG Score
10.0(medium)
EG Risk
60(Track)
EG Risk 60/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 computed
Severity100% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
56%
KEV
Not listed

Published

August 24, 2026

Last Modified

September 15, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit.
github Patch Available🟡 PoC Available

RestrictedPython sandbox bypass via getattr builtin in python_sandbox_server · Advisory · IBM/mcp-context-forge · GitHub

https://github.com/IBM/mcp-context-forge/security/advisories/GHSA-xm98-3vcf-fph7
github_release Patch Available

v1.0.2 - Admin UI Rewrite, Database Migrations, Security Enhancements, and Bug Fixes

Patch available: IBM/mcp-context-forge v1.0.2

https://github.com/IBM/mcp-context-forge/releases/tag/v1.0.2
github_commit

commit 63a2900e6301 (IBM/mcp-context-forge)

Fix landed in IBM/mcp-context-forge commit 63a2900e6301 — awaiting tagged release

https://github.com/IBM/mcp-context-forge/commit/63a2900e6301b9c8a483a38d3737a1beb3a7ce89

Vendor Advisories for CVE-2026-53710(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
mcp-contextforge-gateway0.1.0 ... 1.0.1 (16 versions)1.0.2—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 9× 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-09-18 20:03 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 21:11 UTCEG score recompute
  4. 2026-09-16 19:31 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-15 20:47 UTCEG score recompute
  7. 2026-09-15 19:50 UTCEG score recompute
  8. 2026-09-15 17:34 UTCEG score recompute
  9. 2026-09-02 16:11 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53710?
CVE-2026-53710 is a critical vulnerability published on August 24, 2026. MCP Context Forge is an AI gateway, registry, and proxy for MCP, A2A, REST, and gRPC APIs. Prior to 1.0.2, the pythonsandboxserver in mcp-servers/python/pythonsandboxserver/src/pythonsandboxserver/serverfastmcp.py exposes raw getattr through safebuiltins, omits a required getattr guard, and relies…
When was CVE-2026-53710 disclosed?
CVE-2026-53710 was first published in the National Vulnerability Database on August 24, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53710 actively exploited?
CVE-2026-53710 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 44.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53710?
CVE-2026-53710 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-53710?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53710, 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-53710

Explore →

Is Your Infrastructure Affected by CVE-2026-53710?

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

Start Free Scan →Browse All CVEs