CVE-2026-8355 (GCVE-0-2026-8355)

Vulnerability from cvelistv5 – Published: 2026-10-19 23:42 – Updated: 2026-10-19 23:42
VLAI
Title
IBM ContextForge MCP Gateway is affected by server-side request forgery
Summary
IBM ContextForge MCP Gateway 0.1.0 through 1.0.5 is vulnerable to a server-side request Forgery (SSRF) that allows authenticated users with gateway creation privileges to perform arbitrary HTTP POST requests to internal network resources and cloud metadata endpoints. The vulnerability occurs during OAuth-enabled gateway registration when the system fails to validate the oauth_config.token_url parameter. When registering a gateway with OAuth client credentials authentication, an attacker can supply a malicious token_url pointing to internal services, cloud metadata endpoints (AWS IMDSv1, GCP, Azure), or localhost-bound services. The application immediately performs an HTTP POST request to the attacker-controlled URL with form-encoded credentials in the body. If the response cannot be parsed as a valid OAuth token response, up to 256 characters of the response body are reflected back to the attacker in the HTTP 502 error message. This vulnerability bypasses existing SSRF protections that are applied to the gateway.url field but not to OAuth configuration parameters.
Severity
No CVSS data available.
CWE
  • CWE-918 - Server-Side request forgery (SSRF)
Assigner
ibm CNA under the mitre root
CNA scorecard B 88/100 over 1278 records in the last 180 days details
References
URL Tags
https://www.ibm.com/support/pages/node/7285723 vendor-advisorypatch
Impacted products
Vendor Product Version CPE status
IBM ContextForge MCP Gateway Affected: 0.1.0 , ≤ 1.0.5 (semver)
    cpe:2.3:a:ibm:contextforge_mcp_gateway:*:*:*:*:*:*:*:*
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "ContextForge MCP Gateway",
          "vendor": "IBM",
          "versions": [
            {
              "lessThanOrEqual": "1.0.5",
              "status": "affected",
              "version": "0.1.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:ibm:contextforge_mcp_gateway:*:*:*:*:*:*:*:*",
                  "versionEndIncluding": "1.0.5",
                  "versionStartIncluding": "0.1.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ],
          "operator": "OR"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eIBM ContextForge MCP Gateway 0.1.0 through 1.0.5 is vulnerable to a server-side request Forgery (SSRF) that allows authenticated users with gateway creation privileges to perform arbitrary HTTP POST requests to internal network resources and cloud metadata endpoints. The vulnerability occurs during OAuth-enabled gateway registration when the system fails to validate the oauth_config.token_url parameter. When registering a gateway with OAuth client credentials authentication, an attacker can supply a malicious token_url pointing to internal services, cloud metadata endpoints (AWS IMDSv1, GCP, Azure), or localhost-bound services. The application immediately performs an HTTP POST request to the attacker-controlled URL with form-encoded credentials in the body. If the response cannot be parsed as a valid OAuth token response, up to 256 characters of the response body are reflected back to the attacker in the HTTP 502 error message. This vulnerability bypasses existing SSRF protections that are applied to the gateway.url field but not to OAuth configuration parameters.\u003c/p\u003e"
            }
          ],
          "value": "IBM ContextForge MCP Gateway 0.1.0 through 1.0.5 is vulnerable to a server-side request Forgery (SSRF) that allows authenticated users with gateway creation privileges to perform arbitrary HTTP POST requests to internal network resources and cloud metadata endpoints. The vulnerability occurs during OAuth-enabled gateway registration when the system fails to validate the oauth_config.token_url parameter. When registering a gateway with OAuth client credentials authentication, an attacker can supply a malicious token_url pointing to internal services, cloud metadata endpoints (AWS IMDSv1, GCP, Azure), or localhost-bound services. The application immediately performs an HTTP POST request to the attacker-controlled URL with form-encoded credentials in the body. If the response cannot be parsed as a valid OAuth token response, up to 256 characters of the response body are reflected back to the attacker in the HTTP 502 error message. This vulnerability bypasses existing SSRF protections that are applied to the gateway.url field but not to OAuth configuration parameters."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-918",
              "description": "CWE-918 Server-Side request forgery (SSRF)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T23:42:01.778Z",
        "orgId": "9a959283-ebb5-44b6-b705-dcc2bbced522",
        "shortName": "ibm"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory",
            "patch"
          ],
          "url": "https://www.ibm.com/support/pages/node/7285723"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003e\u003cstrong\u003eIBM strongly recommends addressing the vulnerability now.\u003c/strong\u003e\u003c/p\u003e\u003cdiv\u003e\u003ctable\u003e\u003ctbody\u003e\u003ctr\u003e\u003ctd\u003e\u003cstrong\u003eProduct(s)\u003c/strong\u003e\u003c/td\u003e\u003ctd\u003e\u003cstrong\u003eVersion(s) number and/or range\u00a0\u003c/strong\u003e\u003c/td\u003e\u003ctd\u003e\u003cstrong\u003eRemediation/Fix/Instructions\u003c/strong\u003e\u003c/td\u003e\u003c/tr\u003e\u003ctr\u003e\u003ctd\u003e\u003cdiv\u003e\u003cdiv\u003eIBM ContextForge MCP Gateway\u003c/div\u003e\u003c/div\u003e\u003c/td\u003e\u003ctd\u003e2.0\u0026gt;=v1.0.6\u003c/td\u003e\u003ctd\u003e\u003cdiv\u003e\u003cdiv\u003eUpgrade to v1.0.6 or later. See release notes:\u00a0\u003ca href=\"https://github.com/IBM/mcp-context-forge/releases/tag/v1.0.6%29\" rel=\"nofollow\"\u003ehttps://github.com/IBM/mcp-context-forge/releases/tag/v1.0.6\u003c/a\u003e\u003c/div\u003e\u003c/div\u003e\u003c/td\u003e\u003c/tr\u003e\u003c/tbody\u003e\u003c/table\u003e\u003c/div\u003e\u003cp\u003e\u003c/p\u003e\u003cp\u003e\u003c/p\u003e"
            }
          ],
          "value": "IBM strongly recommends addressing the vulnerability now.\n\nProduct(s)Version(s) number and/or range\u00a0Remediation/Fix/InstructionsIBM ContextForge MCP Gateway\n\n\n\n2.0\u003e=v1.0.6Upgrade to v1.0.6 or later. See release notes:\u00a0 https://github.com/IBM/mcp-context-forge/releases/tag/v1.0.6 https://github.com/IBM/mcp-context-forge/releases/tag/v1.0.6%29"
        }
      ],
      "title": "IBM ContextForge MCP Gateway is affected by server-side request forgery",
      "workarounds": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cdiv\u003e\u003cdiv\u003eIf an immediate upgrade to v1.0.6 is not possible, restrict access to the gateway registration API:\u003c/div\u003e\u003cbr/\u003e\u003cdiv\u003e- Remove the `gateways.create` permission from the `developer` role or any role assigned to untrusted users.\u003c/div\u003e\u003cdiv\u003e- Enforce network-level egress controls (firewall / security group rules) to block outbound HTTP/HTTPS from the gateway host to cloud metadata addresses (`169.254.254.169/32`, `fd00:ec2::254/128`), RFC 1918 ranges, and loopback (`127.0.0.0/8`).\u003c/div\u003e\u003c/div\u003e\u003cdiv\u003e\u003cdiv\u003eIBM strongly recommends upgrading to the fixed version as soon as possible.\u003c/div\u003e\u003c/div\u003e"
            }
          ],
          "value": "If an immediate upgrade to v1.0.6 is not possible, restrict access to the gateway registration API:\n\n\n- Remove the `gateways.create` permission from the `developer` role or any role assigned to untrusted users.\n\n- Enforce network-level egress controls (firewall / security group rules) to block outbound HTTP/HTTPS from the gateway host to cloud metadata addresses (`169.254.254.169/32`, `fd00:ec2::254/128`), RFC 1918 ranges, and loopback (`127.0.0.0/8`).\n\n\n\nIBM strongly recommends upgrading to the fixed version as soon as possible."
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "9a959283-ebb5-44b6-b705-dcc2bbced522",
    "assignerShortName": "ibm",
    "cveId": "CVE-2026-8355",
    "datePublished": "2026-10-19T23:42:01.778Z",
    "dateReserved": "2026-05-11T17:24:26.842Z",
    "dateUpdated": "2026-10-19T23:42:01.778Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-8355",
      "date": "2026-10-20",
      "epss": "0.00182",
      "percentile": "0.07355"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "ContextForge MCP Gateway",
                "vendor": "IBM",
                "versions": [
                  {
                    "lessThanOrEqual": "1.0.5",
                    "status": "affected",
                    "version": "0.1.0",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "psirt@us.ibm.com"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "IBM ContextForge MCP Gateway 0.1.0 through 1.0.5 is vulnerable to a server-side request Forgery (SSRF) that allows authenticated users with gateway creation privileges to perform arbitrary HTTP POST requests to internal network resources and cloud metadata endpoints. The vulnerability occurs during OAuth-enabled gateway registration when the system fails to validate the oauth_config.token_url parameter. When registering a gateway with OAuth client credentials authentication, an attacker can supply a malicious token_url pointing to internal services, cloud metadata endpoints (AWS IMDSv1, GCP, Azure), or localhost-bound services. The application immediately performs an HTTP POST request to the attacker-controlled URL with form-encoded credentials in the body. If the response cannot be parsed as a valid OAuth token response, up to 256 characters of the response body are reflected back to the attacker in the HTTP 502 error message. This vulnerability bypasses existing SSRF protections that are applied to the gateway.url field but not to OAuth configuration parameters."
          }
        ],
        "id": "CVE-2026-8355",
        "lastModified": "2026-10-20T00:19:20.530",
        "metrics": {},
        "published": "2026-10-20T00:19:20.530",
        "references": [
          {
            "source": "psirt@us.ibm.com",
            "url": "https://www.ibm.com/support/pages/node/7285723"
          }
        ],
        "sourceIdentifier": "psirt@us.ibm.com",
        "vulnStatus": "Received",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-918"
              }
            ],
            "source": "psirt@us.ibm.com",
            "type": "Primary"
          }
        ]
      }
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.