CVE-2026-18905

HIGHPre-NVD 7.77.7—
EchelonGraph scoreHIGH confidence

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-09-04. a secondary CVSS source baseline 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.7Exploit: None knownExposed: 0

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

IBM ContextForge MCP Gateway (mcp-contextforge-gateway) <= v1.0.6 MCP Context Forge could allow a remote authenticated attacker to obtain sensitive information due to a DNS rebinding vulnerability during tool invocation.

CVSS v3
7.7
EG Score
7.7(high)
EG Risk
35(Track)
EG Risk 35/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
Severity77% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

September 4, 2026

Last Modified

September 15, 2026

Advisory Details (1)

Auto-updated Sep 4, 2026
No patch confirmed yet.
generic

Security Bulletin: IBM ContextForge MCP Gateway is affected by server-side request forgery via DNS TOCTOU at tool invocation

https://www.ibm.com/support/pages/node/7286053

Vendor Advisories for CVE-2026-18905(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 24× in last 7d / 66× 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-20 19:36 UTCGHSA enrichment
  2. 2026-09-20 08:23 UTCGHSA enrichment
  3. 2026-09-19 21:09 UTCEG score recompute
  4. 2026-09-19 21:09 UTCGHSA enrichment
  5. 2026-09-19 09:55 UTCGHSA enrichment
  6. 2026-09-18 22:38 UTCEG score recompute
  7. 2026-09-18 22:38 UTCGHSA enrichment
  8. 2026-09-18 19:27 UTCEPSS rescore
  9. 2026-09-18 11:26 UTCGHSA enrichment
  10. 2026-09-18 00:13 UTCEG score recompute
  11. 2026-09-18 00:13 UTCGHSA enrichment
  12. 2026-09-17 13:00 UTCGHSA enrichment
  13. 2026-09-17 01:14 UTCEG score recompute
  14. 2026-09-17 01:14 UTCGHSA enrichment
  15. 2026-09-16 14:07 UTCEPSS rescore
  16. 2026-09-16 14:01 UTCEG score recompute
  17. 2026-09-16 14:01 UTCGHSA enrichment
  18. 2026-09-16 05:14 UTCEPSS rescore
  19. 2026-09-16 02:47 UTCGHSA enrichment
  20. 2026-09-15 15:34 UTCGHSA enrichment
  21. 2026-09-15 05:35 UTCEG score recompute
  22. 2026-09-15 05:35 UTCGHSA enrichment
  23. 2026-09-14 18:22 UTCGHSA enrichment
  24. 2026-09-14 06:24 UTCGHSA enrichment
  25. 2026-09-13 19:11 UTCEG score recompute
Show 41 more
  1. 2026-09-13 19:11 UTCGHSA enrichment
  2. 2026-09-13 16:46 UTCEPSS rescore
  3. 2026-09-13 07:57 UTCGHSA enrichment
  4. 2026-09-12 20:45 UTCEG score recompute
  5. 2026-09-12 20:45 UTCGHSA enrichment
  6. 2026-09-12 15:00 UTCEPSS rescore
  7. 2026-09-12 09:32 UTCGHSA enrichment
  8. 2026-09-11 22:18 UTCGHSA enrichment
  9. 2026-09-11 11:04 UTCEG score recompute
  10. 2026-09-11 11:04 UTCGHSA enrichment
  11. 2026-09-11 09:36 UTCEPSS rescore
  12. 2026-09-10 23:50 UTCGHSA enrichment
  13. 2026-09-10 12:10 UTCEG score recompute
  14. 2026-09-10 12:10 UTCGHSA enrichment
  15. 2026-09-10 09:34 UTCEPSS rescore
  16. 2026-09-10 00:57 UTCGHSA enrichment
  17. 2026-09-09 13:44 UTCGHSA enrichment
  18. 2026-09-09 02:30 UTCEG score recompute
  19. 2026-09-09 02:30 UTCGHSA enrichment
  20. 2026-09-08 22:00 UTCEPSS rescore
  21. 2026-09-08 15:15 UTCGHSA enrichment
  22. 2026-09-08 13:20 UTCGHSA enrichment
  23. 2026-09-08 02:06 UTCEG score recompute
  24. 2026-09-08 02:06 UTCGHSA enrichment
  25. 2026-09-07 16:01 UTCEPSS rescore
  26. 2026-09-07 14:52 UTCGHSA enrichment
  27. 2026-09-07 03:39 UTCGHSA enrichment
  28. 2026-09-06 16:21 UTCEG score recompute
  29. 2026-09-06 16:21 UTCGHSA enrichment
  30. 2026-09-06 13:47 UTCEPSS rescore
  31. 2026-09-06 05:08 UTCGHSA enrichment
  32. 2026-09-05 17:55 UTCEG score recompute
  33. 2026-09-05 17:55 UTCGHSA enrichment
  34. 2026-09-05 06:41 UTCGHSA enrichment
  35. 2026-09-04 19:19 UTCEG score recompute
  36. 2026-09-04 19:19 UTCGHSA enrichment
  37. 2026-09-04 18:40 UTCEG score recompute
  38. 2026-09-04 18:39 UTCGHSA enrichment
  39. 2026-09-04 16:24 UTCEG score recompute
  40. 2026-09-04 16:05 UTCEG score recompute
  41. 2026-09-04 16:04 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18905?
CVE-2026-18905 is a high vulnerability published on September 4, 2026. IBM ContextForge MCP Gateway (mcp-contextforge-gateway) <= v1.0.6 MCP Context Forge could allow a remote authenticated attacker to obtain sensitive information due to a DNS rebinding vulnerability during tool invocation.
When was CVE-2026-18905 disclosed?
CVE-2026-18905 was first published in the National Vulnerability Database on September 4, 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-18905 actively exploited?
CVE-2026-18905 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.6% of all scored CVEs.
What is the CVSS score of CVE-2026-18905?
CVE-2026-18905 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-18905?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18905, 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

Explore the affected products and dependency analysis for CVE-2026-18905

Explore →

Is Your Infrastructure Affected by CVE-2026-18905?

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

Start Free Scan →Browse All CVEs