Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-11918IBM ContextForge MCP Gateway is affected by security filter bypass via nested payload structures

Description

IBM ContextForge MCP Gateway <= v1.0.4 IBM mcp-context-forge could allow an authenticated user to bypass protection mechanisms due to incomplete recursive inspection of nested payload content.

Timeline

  1. ID reserved

    By ibm

  2. · 3 months later

    Published

  3. · 5 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-11918, by who scored it
Scored byCVSSScoreVector
ibmCNA (assigner)3.1Medium5.4CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
NVDNVD · Analyzed3.1Medium6.5CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.4.

Affected products

What to do

Solution: | Product | Affected Version(s) | Fix Version | Instructions | |---|---|---|---| | | <=1.0.4 | 1.0.5 | Upgrade to v1.0.5 or later. . | IBM strongly recommends addressing the vulnerability now. Product(s)Version(s) number and/or range Remediation/Fix/InstructionsIBM ContextForge MCP Gateway<=1.0.4 v1.0.5 or later See [release notes]( https://github.com/IBM/mcp-context-forge/releases/tag/v1.0.5) https://github.com/IBM/mcp-context-forge/releases/tag/v1.0.5%29  Note: <Component A / B names> are bundled with <Product profile name> to provide <feature / function description>

Workaround: There is no workaround that fully prevents the bypass while keeping the affected plugins active. Operators may disable `regex_filter` and `deny_filter` in `plugins/config.yaml` to prevent exploitation, at the cost of losing the filtering controls those plugins provide. IBM strongly recommends upgrading to v1.0.5 or higher, which replaces the top-level-only scan loops with a recursive walker in both plugins.

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-11918 badge
[![CVE-2026-11918](https://cveledger.app/badge/CVE-2026-11918.svg)](https://cveledger.app/cve/CVE-2026-11918)

Record last updated .