{"answers":{"affected":"3 open source packages ship an affected version, including utcp-http.","exploited":"There is no known exploitation of CVE-2026-44661 in the wild and no public exploit code.","fix":"Upgrade utcp-http to 1.1.2 or later.","what":"CVE-2026-44661 is a medium-severity server-side request forgery vulnerability in universal-tool-calling-protocol python-utcp, published on 14 May 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-44661 and fix it if it is affected.\n\nWhat it is: CVE-2026-44661 is a medium-severity server-side request forgery vulnerability in universal-tool-calling-protocol python-utcp, published on 14 May 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-44661 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- utcp-http (PyPI): affected all versions; fixed in 1.1.2\n- utcp-http (PyPI): affected all versions; fixed in 1.1.2\n- utcp-http (PyPI): affected all versions; fixed in 1.1.2\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-44661/ (Markdown: https://insights.sbomify.com/CVE-2026-44661/index.md)","id":"CVE-2026-44661","markdown":"https://insights.sbomify.com/CVE-2026-44661/index.md","name":"CVE-2026-44661","record":{"aliases":["GHSA-39j6-4867-gg4w","PYSEC-2026-3396"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python UTCP library","requires_auth":"none","summary":"Attackers can force the library to make requests to internal services by hosting malicious OpenAPI specs, bypassing URL validation checks.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"python-utcp is the python implementation of UTCP. Prior to 1.1.3, the utcp-http plugin is vulnerable to a blind Server-Side Request Forgery (SSRF) caused by a trust-boundary inconsistency between manual discovery and tool invocation. register_manual() validates the discovery URL against an HTTPS / loopback allowlist, but call_tool() and call_tool_streaming() reuse the resolved tool_call_template.url directly without revalidating, and the OpenAPI converter blindly trusts whatever servers[0].url an attacker-hosted spec declares. An attacker who hosts a malicious OpenAPI spec on a legitimate HTTPS endpoint can declare e.g. servers: [{ url: \"http://127.0.0.1:9090\" }] or servers: [{ url: \"http://169.254.169.254\" }]; the OpenAPI converter then produces tools whose URL points at internal services on the agent host. All three HTTP-class protocols (utcp_http.http, utcp_http.streamable_http, utcp_http.sse) shared the same gap. This vulnerability is fixed in 1.1.3.","ecosystems":["PyPI"],"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":"python-utcp: SSRF via attacker-controlled OpenAPI servers[0].url in HTTP communication protocol","id":"CVE-2026-44661","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"rust-openssl: Heap buffer overflow when encrypting with AES key-wrap-with-padding","id":"CVE-2026-44662"},"packages":[{"ecosystem":"PyPI","fixed":["1.1.2"],"introduced":["0"],"last_affected":[],"package":"utcp-http","purl":null,"source":"GHSA-39j6-4867-gg4w"},{"ecosystem":"PyPI","fixed":["1.1.2"],"introduced":["0"],"last_affected":[],"package":"utcp-http","purl":"pkg:pypi/utcp-http","source":"GHSA-39j6-4867-gg4w"},{"ecosystem":"PyPI","fixed":["1.1.2"],"introduced":["0"],"last_affected":[],"package":"utcp-http","purl":"pkg:pypi/utcp-http","source":"PYSEC-2026-3396"}],"prev":{"headline":"UltraJSON: Memory Leak in ujson.dump() on Write Failure","id":"CVE-2026-44660"},"products":["python-utcp"],"published":"2026-05-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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-05-15","vendors":["universal-tool-calling-protocol"]},"summary":"Attackers can force the library to make requests to internal services by hosting malicious OpenAPI specs, bypassing URL validation checks.","url":"https://insights.sbomify.com/CVE-2026-44661/"}