{"answers":{"affected":"1 open source package ship an affected version, including consul.","exploited":"There is no known exploitation of CVE-2026-16328 in the wild and no public exploit code.","fix":"Upgrade consul to 0.1.4 or later.","what":"CVE-2026-16328 is a high-severity server-side request forgery vulnerability in HashiCorp Tooling, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-16328 and fix it if it is affected.\n\nWhat it is: CVE-2026-16328 is a high-severity server-side request forgery vulnerability in HashiCorp Tooling, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-16328 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- consul (Bitnami): affected from 0.1.0; fixed in 0.1.4\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-16328/ (Markdown: https://insights.sbomify.com/CVE-2026-16328/index.md)","id":"CVE-2026-16328","markdown":"https://insights.sbomify.com/CVE-2026-16328/index.md","name":"CVE-2026-16328","record":{"aliases":["BIT-consul-2026-16328","GHSA-5h6c-295f-7pp3"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Consul MCP server","requires_auth":"none","summary":"A malicious client can redirect Consul API traffic to an attacker-controlled endpoint, potentially exposing the server's Consul token.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HashiCorp","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"In consul-mcp-server, versions 0.1.0 up to 0.1.3 did not restrict how the Consul backend address was supplied, allowing a connected client to override the server's configured Consul address via a request header. This may allow a malicious client to redirect the server's Consul API traffic to an attacker-controlled endpoint, potentially exfiltrating the Consul token configured on the server. This vulnerability, CVE-2026-16328, is fixed in consul-mcp-server 0.1.4.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"consul-mcp-server vulnerable to server side request forgery leading to token exposure","id":"CVE-2026-16328","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":1,"n_references":1,"next":{"headline":"D-Link DNS-320 uploadify.php unrestricted upload","id":"CVE-2026-16329"},"packages":[{"ecosystem":"Bitnami","fixed":["0.1.4"],"introduced":["0.1.0"],"last_affected":[],"package":"consul","purl":"pkg:bitnami/consul","source":"BIT-consul-2026-16328"}],"prev":{"headline":"D-Link DNS-320 upload.php unrestricted upload","id":"CVE-2026-16327"},"products":["Tooling"],"published":"2026-07-29","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-29","vendors":["HashiCorp"]},"summary":"A malicious client can redirect Consul API traffic to an attacker-controlled endpoint, potentially exposing the server's Consul token.","url":"https://insights.sbomify.com/CVE-2026-16328/"}