{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19765 exists.","fix":"No fix has been published for CVE-2026-19765 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-19765 is a medium-severity server-side request forgery vulnerability in eyaushev swagger-testcase-mcp, published on 14 Aug 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-19765 and fix it if it is affected.\n\nWhat it is: CVE-2026-19765 is a medium-severity server-side request forgery vulnerability in eyaushev swagger-testcase-mcp, published on 14 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19765 exists.\n\nAffected product: eyaushev swagger-testcase-mcp. 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-19765/ (Markdown: https://insights.sbomify.com/CVE-2026-19765/index.md)","id":"CVE-2026-19765","markdown":"https://insights.sbomify.com/CVE-2026-19765/index.md","name":"CVE-2026-19765","record":{"aliases":["GHSA-4324-vhrx-x39p"],"analysis":{"component_type":"developer_tool","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MCP server tool","requires_auth":"low_privilege","summary":"Remote attackers can exploit a server-side request forgery flaw in the swagger-testcase-mcp tool to access internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A security flaw has been discovered in eyaushev swagger-testcase-mcp 5babb27c951fb404bc2b25ec80593616e49054e5. This vulnerability affects the function loadSource of the file src/utils/swagger-parser.ts of the component fetch_swagger. Performing a manipulation results in server-side request forgery. The attack is possible to be carried out remotely. The exploit has been released to the public and may be used for attacks. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project was informed of the problem early through an issue report but has not responded yet.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"eyaushev swagger-testcase-mcp fetch_swagger swagger-parser.ts loadSource server-side request forgery","id":"CVE-2026-19765","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Authentication Bypass leads to Administrative control of adjacent network hosts in HPE Networking Fabric Composer","id":"CVE-2026-19766"},"packages":[],"prev":{"headline":"Raisecom Communication Command and Dispatch Management Platform getpwd.php sql injection","id":"CVE-2026-19764"},"products":["swagger-testcase-mcp"],"published":"2026-08-14","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["eyaushev"]},"summary":"Remote attackers can exploit a server-side request forgery flaw in the swagger-testcase-mcp tool to access internal resources.","url":"https://insights.sbomify.com/CVE-2026-19765/"}