CVE-2026-129094 in utcp-httpinfo

Summary

by MITRE • 11/13/2026

@utcp/http before 1.1.14 contains a server-side request forgery vulnerability that allows remote manuals to reach loopback services by bypassing the remote-loopback check with a {host} placeholder. Attackers can supply host arguments like 127.0.0.1 or register tools via Streamable HTTP and SSE discovery to access internal services on the agent machine.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/13/2026

The @utcp/http library, prior to version 1.1.14, contains a critical server-side request forgery vulnerability that stems from an insufficient validation of host parameters during outbound network requests. This flaw allows attackers to bypass standard remote-loopback checks by exploiting the handling of placeholder variables within URL structures. Specifically, when a developer utilizes a {host} placeholder in their code and passes it through this library's HTTP client functions without adequate sanitization or strict allow-listing, the underlying implementation fails to properly resolve or restrict the target address before initiating the connection. This oversight creates a pathway for malicious actors to redirect requests intended for external resources toward internal infrastructure components that are otherwise inaccessible from outside the local network perimeter.

The technical mechanism of this exploitation relies on the library's failure to enforce strict host validation after variable substitution occurs. By supplying specific arguments such as 127.0.0.1 or localhost, an attacker can force the application to make requests to services running on the loopback interface of the agent machine where the vulnerable code is executing. This bypasses security controls that typically prevent external inputs from triggering internal network traffic, effectively turning the server into a proxy for accessing sensitive local endpoints. The vulnerability is particularly dangerous because it does not require complex payload construction; simple manipulation of host arguments is sufficient to achieve unauthorized access to internal services.

The operational impact of this vulnerability can be severe, depending on what services are exposed on the loopback interface of the affected agent machine. Attackers who successfully exploit this flaw can interact with administrative interfaces, database connections, or other sensitive APIs that rely solely on local network restrictions for security. This could lead to unauthorized data access, modification of critical system configurations, or further lateral movement within a private network if those internal services are interconnected. In environments where Streamable HTTP and SSE discovery mechanisms are employed, the risk is amplified as attackers can register tools via these protocols to automate the probing and exploitation of multiple internal endpoints without detection by traditional perimeter security measures.

This vulnerability aligns with CWE-918, which addresses Server-Side Request Forgery (SSRF), specifically falling under scenarios where server-side code makes requests based on user-supplied input without proper validation of the destination host. From a threat intelligence perspective, this behavior is consistent with ATT&CK technique T1557, Adversary-in-the-Middle, as it enables an attacker to position themselves between clients and internal services or to access resources that are not directly exposed to the internet but are reachable from within the network environment via loopback interfaces. The exploitation of such vulnerabilities often serves as a precursor to more advanced attacks, including credential theft or full system compromise through trusted local service interactions.

To mitigate this vulnerability, organizations must immediately upgrade @utcp/http to version 1.1.14 or later, where these validation checks have been corrected. For applications that cannot be updated instantly, developers should implement strict allow-listing of permitted hostnames and IP addresses at the application layer before passing them to any HTTP client functions. It is crucial to validate not only the final resolved address but also the input parameters themselves to ensure they do not contain loopback indicators or private network ranges unless explicitly intended for internal communication that has been secured through additional authentication mechanisms. Additionally, reviewing codebases for usage of {host} placeholders and similar dynamic variable substitutions in HTTP requests will help identify other potential instances where this bypass could occur.

Responsible

VulnCheck

Reservation

11/13/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00236

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!