CVE-2026-16125: Server-Side Request Forgery in zevorn rt-claw
A critical server-side request forgery (SSRF) vulnerability, identified as CVE-2026-16125, affects zevorn rt-claw versions up to and including 0.2.0, residing in the claw_net_get/claw_net_post functions within the http_request component, allowing remote attackers to manipulate the URL argument and access internal resources or perform port scanning.
What's new
A significant server-side request forgery (SSRF) vulnerability, tracked as CVE-2026-16125, has been identified in zevorn rt-claw software, specifically impacting versions up to and including 0.2.0. This flaw exists within the claw_net_get and claw_net_post functions located in the claw/services/tools/net.c file, part of the application's http_request component. Attackers can remotely exploit this vulnerability by manipulating the url argument, leading to the application making requests to arbitrary internal or external destinations. This allows adversaries to bypass network access controls, gather sensitive information, or interact with services not intended for public exposure. An exploit for CVE-2026-16125 has been publicly released, increasing the urgency for users to address this vulnerability to prevent potential compromise of internal systems.
Attack Chain
- Attacker identifies an internet-facing zevorn rt-claw application instance running version 0.2.0 or earlier.
- Attacker crafts a specially formed HTTP request targeting the vulnerable
claw_net_getorclaw_net_postfunctions. - The crafted request includes a manipulated
urlargument containing an arbitrary internal IP address, hostname, or sensitive service endpoint. - The zevorn rt-claw application processes this malicious
urlparameter without adequate validation or sanitization. - The application's
http_requestcomponent then makes an unintended, server-side outbound connection to the attacker-specified internal or external resource. - This server-side request forgery (SSRF) allows the attacker to bypass network segmentation, probe internal services, or access metadata services (e.g., cloud instance metadata).
- The final objective can range from internal network reconnaissance and information disclosure to potential further exploitation of discovered internal services or exfiltration of sensitive data.
Impact
A successful exploitation of CVE-2026-16125 can have severe consequences, rated with a CVSS v3.1 Base Score of 7.3 (High). The primary impact includes unauthorized access to internal network resources, bypassing network firewalls and segmentation. Attackers can use this vulnerability to perform port scanning of internal hosts, access sensitive web services, or retrieve cloud provider metadata, which often contains credentials or configuration details. This can lead to significant information disclosure, lateral movement within the network, and potentially complete system compromise, enabling further sophisticated attacks against the organization's infrastructure.
Recommendation
- Patch CVE-2026-16125 immediately by updating zevorn rt-claw to a version greater than 0.2.0, once released by the vendor.
- Monitor your webserver logs for the
rt-clawapplication for unusualurlparameters containing internal IP addresses, non-standard ports, or suspicious domain names.
Detection coverage 1
Detect CVE-2026-16127 Exploitation - Zevorn RT-Claw SSRF Attempt
highDetects CVE-2026-16127 exploitation - Server-Side Request Forgery vulnerability in zevorn rt-claw, by monitoring web server logs for suspicious URL arguments targeting internal resources.
Detection queries are available on the platform. Get full rules →
Indicators of compromise
2
8
url
| Type | Value |
|---|---|
| url | https://github.com/zevorn/rt-claw/ |
| url | https://github.com/zevorn/rt-claw/issues/135 |
| url | https://github.com/zevorn/rt-claw/issues/137 |
| url | https://vuldb.com/cve/CVE-2026-16126 |
| url | https://vuldb.com/submit/856870 |
| url | https://vuldb.com/submit/856871 |
| url | https://vuldb.com/vuln/379838 |
| url | https://vuldb.com/vuln/379838/cti |
| nvd@nist.gov | |
| soc@us-cert.gov |