{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-8355 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-8355 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-8355 is a medium-severity server-side request forgery vulnerability in IBM ContextForge MCP Gateway, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-8355 and fix it if it is affected.\n\nWhat it is: CVE-2026-8355 is a medium-severity server-side request forgery vulnerability in IBM ContextForge MCP Gateway, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-8355 in the wild and no public exploit code.\n\nAffected product: IBM ContextForge MCP Gateway. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-8355/ (Markdown: https://insights.sbomify.com/CVE-2026-8355/index.md)","id":"CVE-2026-8355","markdown":"https://insights.sbomify.com/CVE-2026-8355/index.md","name":"CVE-2026-8355","record":{"aliases":["GHSA-6f4r-8687-5x9p"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MCP Gateway","requires_auth":"low_privilege","summary":"Authenticated users can exploit SSRF in IBM ContextForge MCP Gateway to access internal resources and cloud metadata via unvalidated OAuth token URLs.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"IBM ContextForge MCP Gateway is affected by server-side request forgery","id":"CVE-2026-8355","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Stack buffer overflow in PPT presentation import","id":"CVE-2026-8356"},"packages":[],"prev":{"headline":"Cross-site scripting in Gum Addon for Elementor","id":"CVE-2026-8354"},"products":["ContextForge MCP Gateway"],"published":"2026-10-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["IBM"]},"summary":"Authenticated users can exploit SSRF in IBM ContextForge MCP Gateway to access internal resources and cloud metadata via unvalidated OAuth token URLs.","url":"https://insights.sbomify.com/CVE-2026-8355/"}