{"schema":"voidly-atlas-federal-record/v1","dataset":"nvd-cves","agency":"NIST","source":"NIST National Vulnerability Database","provider":"Voidly","license":"Source data is U.S. federal public domain (17 U.S.C. §105). Re-surfaced by Voidly under CC BY 4.0.","disclaimer":"This is the agency's own public-domain data, curated and made citable by Voidly. Voidly adds no independent claim — always verify against the linked canonical source.","generated_at":"2026-10-20T15:11:50.986Z","record":{"id":"CVE-2026-8355","cve_id":"CVE-2026-8355","published":"2026-10-20T00:19:20.530","last_modified":"2026-10-20T00:19:20.530","status":"Received","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.","cvss_score":null,"cvss_severity":null,"cvss_vector":null,"cwes":"CWE-918","cpe_count":0,"source_url":"https://nvd.nist.gov/vuln/detail/CVE-2026-8355","voidly_url":"https://voidly.ai/atlas/federal/nvd-cves/CVE-2026-8355"},"citation":{"voidly_url":"https://voidly.ai/atlas/federal/nvd-cves/CVE-2026-8355","source_url":"https://nvd.nist.gov/vuln/detail/CVE-2026-8355","recommended":"CVE-2026-8355 — CVE. NIST, via Voidly Atlas — Surveillance & Digital-Rights Watch. Retrieved 2026-10-20, https://voidly.ai/atlas/federal/nvd-cves/CVE-2026-8355","ris":"TY  - DATA\nTI  - CVE-2026-8355 — CVE\nAU  - Voidly\nT2  - Voidly Atlas — Surveillance & Digital-Rights Watch\nPB  - Voidly\nPY  - 2026\nUR  - https://voidly.ai/atlas/federal/nvd-cves/CVE-2026-8355\nN1  - Source: NIST National Vulnerability Database, https://nvd.nist.gov/vuln/detail/CVE-2026-8355. Public domain (17 U.S.C. §105); re-surfaced under CC BY 4.0\nER  - ","apa":"Voidly. (2026). CVE-2026-8355 — CVE [NIST National Vulnerability Database]. Voidly Atlas. Retrieved 2026-10-20, from https://voidly.ai/atlas/federal/nvd-cves/CVE-2026-8355","bibtex":"@misc{voidly_nvd_cves_CVE20268355,\n  title        = {CVE-2026-8355 — CVE},\n  author       = {{Voidly}},\n  howpublished = {\\url{https://voidly.ai/atlas/federal/nvd-cves/CVE-2026-8355}},\n  note         = {Source: NIST National Vulnerability Database, https://nvd.nist.gov/vuln/detail/CVE-2026-8355. Public domain (17 U.S.C. §105); re-surfaced under CC BY 4.0},\n  urldate      = {2026-10-20},\n  year         = {2026}\n}"}}