CVE-2026-44661: python-utcp: SSRF via attacker-controlled OpenAPI servers[0].url in HTTP communication protocol
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
- Fixed version: universal-tool-calling-protocol python-utcp 1.1.3.
Low priority for now. Upgrade to universal-tool-calling-protocol python-utcp 1.1.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 14, 2026
- Updated
- Oct 26, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-918
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 4.7
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
universal-tool-calling-protocol python-utcp
- < 1.1.2affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| PyPI | utcp-http | before 1.1.2 | 1.1.2 |
Same product
universal-tool-calling-protocol: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-101060python-utcp before 1.1.4 SSRF via unvalidated HTTP redirects33Monitor
- CVE-2026-45369python-utcp: Command Injection via Unsanitized Argument Substitution in CLI Communication Protocol33Monitor
- CVE-2026-45370python-utcp: Full Process Environment Exposed to CLI Subprocess - Secrets Leakage via Command Injection30Monitor
Published before and after this one in the same product
- Later →CVE-2026-12210Jun 14, 2026 · universal-tool-calling-protocol python-utcp utcp-gql/utcp-websocket server-side request forgery8Monitor
- Later →CVE-2026-101057Sep 27, 2026 · utcp-mcp before 1.1.3 SSRF via unvalidated MCP server URL9Monitor
- Later →CVE-2026-101058Sep 27, 2026 · python-utcp before 1.1.12 SSRF via Remote HTTP Manual28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| universal-tool-calling-protocol python-utcp | 1.1.3 · description | Vendor (CNA) |
| PyPI:utcp-http | 1.1.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-101060136 days apartpython-utcp before 1.1.4 SSRF via unvalidated HTTP redirects33Monitor
- CVE-2026-101058136 days apartpython-utcp before 1.1.12 SSRF via Remote HTTP Manual28Monitor
- CVE-2026-101059136 days apartutcp-http before 1.1.4 OAuth2 tokenUrl Trust Boundary Bypass28Monitor
- CVE-2026-101061136 days apartutcp-gql and utcp-websocket before 1.1.1 SSRF via URL validation bypass9Monitor
- CVE-2026-1221031 days apartuniversal-tool-calling-protocol python-utcp utcp-gql/utcp-websocket server-side request forgery8Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.