Server-Side Request Forgery in zevorn rt-claw HTTP Handler

A security flaw has been discovered in zevorn rt-claw up to 0.2.0. This impacts the function receiver_thread of the file claw/services/swarm/swarm.c of the component http_request. Performing a manipulation results in server-side request forgery. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Casky was already ahead

This CVE exploits attack patterns that Casky's 331matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

CVE-2026-16128 exposes a server-side request forgery (SSRF) vulnerability in zevorn rt-claw versions up to 0.2.0, specifically within the HTTP request receiver thread component. This flaw allows remote attackers to manipulate the function receiver_thread in claw/services/swarm/swarm.c, enabling them to forge requests from the vulnerable server to internal or external resources. SSRF vulnerabilities are critical because they can bypass network segmentation, access internal services, exfiltrate sensitive data, or pivot to attack infrastructure that should be isolated from the internet. Any organization deploying rt-claw for HTTP request handling—particularly in microservices, API gateway, or distributed swarm architectures—faces immediate risk, especially since the exploit is publicly available and the maintainers have not yet addressed the issue.

Casky's 331 matching skills leverage Claude AI's extended reasoning to map this vulnerability across MITRE ATT&CK techniques TA0001 (Initial Access) and TA0006 (Credential Access). Practitioners using Casky would observe detection patterns tied to suspicious outbound requests originating from the vulnerable rt-claw process—particularly requests to internal IP ranges, localhost services, or cloud metadata endpoints (169.254.169.254 for AWS). The platform would flag anomalous HTTP request patterns in receiver_thread logs showing unexpected destination hosts, authentication token exfiltration attempts, or probing of internal service endpoints. By correlating these behavioral indicators with the vulnerability's attack surface, Casky enables teams to identify exploitation attempts before lateral movement or data compromise occurs, providing visibility into both the reconnaissance phase and active exploitation tactics.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

331 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-16128.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0006

Investigate the attack patterns behind CVE-2026-16128

Casky has 331 skills that investigate the attack patterns behind CVE-2026-16128. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn