8.6
Medium
openclaw

CVE-2026-44116

CVE-2026-44116 is a medium-severity server-side request forgery (SSRF) vulnerability in openclaw (npm), affecting versions <= 2026.4.21. It is fixed in 2026.4.22.

Key facts
CVSS score
8.6
Medium
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
openclaw
Fixed in
2026.4.22
Disclosed
2026

Summary

Summary Zalo outbound photo URLs are validated through the SSRF guard. Affected Packages / Versions Package: openclaw (npm) Affected versions: <= 2026.4.21 Fixed version: 2026.4.22 Impact The Zalo plugin could forward an attacker-controlled outbound photo URL to the Zalo Bot API without first applying OpenClaw's SSRF validation policy. Fix Zalo sendPhoto now parses and validates outbound photo URLs with the shared SSRF hostname policy before posting to Zalo, and media-reply paths route through the guarded outbound media helpers. Fix Commit(s) a65eb1b864b7630c1242a82de9e5799b80583c3f Verification The fix commit is contained in the public v2026.4.22 tag. [email protected] is published on npm and the compiled package contains the fix. Focused regression coverage for this path passed before publication. OpenClaw thanks @foodlook for reporting.

Impact

What is server-side request forgery (SSRF)?

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

Severity and exposure

CVE-2026-44116 has a CVSS score of 8.6 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (2026.4.22). Upgrading removes the vulnerable code path.

Affected versions

npm

  • openclaw (<= 2026.4.21)

Security releases

  • openclaw → 2026.4.22 (npm)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-44116 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-44116 is reachable in your applications. Get a demo

Remediation advice

Upgrade openclaw to 2026.4.22 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-44116

What is CVE-2026-44116?

CVE-2026-44116 is a medium-severity server-side request forgery (SSRF) vulnerability in openclaw (npm), affecting versions <= 2026.4.21. It is fixed in 2026.4.22. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.

How severe is CVE-2026-44116?

CVE-2026-44116 has a CVSS score of 8.6 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of openclaw are affected by CVE-2026-44116?

openclaw (npm) versions <= 2026.4.21 is affected.

Is there a fix for CVE-2026-44116?

Yes. CVE-2026-44116 is fixed in 2026.4.22. Upgrade to this version or later.

Is CVE-2026-44116 exploitable, and should I be worried?

Whether CVE-2026-44116 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-44116 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-44116?

Upgrade openclaw to 2026.4.22 or later.

Stop the waste.
Protect your environment with Kodem.