{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-101058 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-101058 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-101058 is a high-severity server-side request forgery vulnerability in universal-tool-calling-protocol python-utcp, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-101058 and fix it if it is affected.\n\nWhat it is: CVE-2026-101058 is a high-severity server-side request forgery vulnerability in universal-tool-calling-protocol python-utcp, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-101058 in the wild and no public exploit code.\n\nAffected product: universal-tool-calling-protocol python-utcp. 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-101058/ (Markdown: https://insights.sbomify.com/CVE-2026-101058/index.md)","id":"CVE-2026-101058","markdown":"https://insights.sbomify.com/CVE-2026-101058/index.md","name":"CVE-2026-101058","record":{"aliases":["GHSA-88pp-fjxx-6p68"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python UTCP library","requires_auth":"none","summary":"An attacker can trick a victim into registering a malicious UTCP manual, causing the client to send requests to local loopback services and return their data.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"python-utcp (pip package utcp-http) before 1.1.12 does not verify whether tool URLs declared in a hand-written UTCP manual point at the agent's own loopback interface when that manual is discovered from a remote, non-loopback origin. Because ensure_secure_url intentionally permits loopback HTTP for local development and native manuals bypassed the loopback check performed by the OpenAPI converter, an attacker who can serve a UTCP manual that a victim registers can cause the client to issue requests to services bound only to 127.0.0.1 on the victim host and have the response bodies returned to the caller (server-side request forgery). The http, sse and streamable_http protocols are all affected. Reach is limited to loopback, and exploitation further requires a loopback service that answers unauthenticated requests with useful data. Fixed in utcp-http 1.1.12, which rejects manuals fetched from a non-loopback origin that declare loopback tool URLs, keyed off the final post-redirect discovery URL.","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":"python-utcp before 1.1.12 SSRF via Remote HTTP Manual","id":"CVE-2026-101058","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"utcp-http before 1.1.4 OAuth2 tokenUrl Trust Boundary Bypass","id":"CVE-2026-101059"},"packages":[],"prev":{"headline":"utcp-mcp before 1.1.3 SSRF via unvalidated MCP server URL","id":"CVE-2026-101057"},"products":["python-utcp"],"published":"2026-09-27","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-09-30","vendors":["universal-tool-calling-protocol"]},"summary":"An attacker can trick a victim into registering a malicious UTCP manual, causing the client to send requests to local loopback services and return their data.","url":"https://insights.sbomify.com/CVE-2026-101058/"}