CVE-2026-22181: OpenClaw < 2026.3.2 - DNS Pinning Bypass via Environment Proxy Configuration in web_fetch
OpenClaw versions prior to 2026.3.2 contain a DNS pinning bypass vulnerability in strict URL fetch paths that allows attackers to circumvent SSRF guards when environment proxy variables are configured. When HTTP_PROXY, HTTPS_PROXY, or ALL_PROXY environment variables are present, attacker-influenced URLs can be routed through proxy behavior instead of pinned-destination routing, enabling access to internal targets reachable from the proxy environment.
Security readout for executives and security teams
Plain-English summary
OpenClaw can mishandle protected URL fetching when proxy environment variables are set. A lower-privileged attacker who can influence fetched URLs may bypass SSRF protections and reach internal systems available through that proxy path. The issue is high severity because it can expose sensitive internal resources.
Executive priority
Treat as a near-term remediation item for internet-facing or multi-user OpenClaw deployments. The risk is strongest where proxies can reach internal services, because SSRF control bypass may expose sensitive internal data or limited integrity and availability impact.
Technical view
Versions before 2026.3.2 have a DNS pinning bypass in strict URL fetch paths. With HTTP_PROXY, HTTPS_PROXY, or ALL_PROXY configured, attacker-influenced URLs may follow proxy behavior instead of pinned-destination routing, weakening SSRF controls. CVSS is 7.6 high, mapped to CWE-918.
Likely exposure
Likely exposure is OpenClaw before 2026.3.2, especially deployments using web_fetch or strict URL fetch behavior with attacker-influenced URLs and proxy environment variables configured. Impact depends on what the proxy environment can reach internally.
Exploitation context
The provided bundle does not show CISA KEV listing or active exploitation. The attack requires low privileges, network access, no user interaction, and a deployment configuration where proxy environment variables influence fetch routing.
Researcher notes
Evidence supports a configuration-dependent SSRF bypass, not a universal remote compromise. Validate version, proxy environment, URL-control paths, and proxy reachability. Avoid assuming exploit activity, affected forks, or mitigations beyond the advisory and fixed release.
Mitigation direction
Upgrade OpenClaw to 2026.3.2 or later.
Review the GitHub advisory and patch commit for vendor guidance.
Remove unnecessary HTTP_PROXY, HTTPS_PROXY, and ALL_PROXY variables from OpenClaw runtimes.
Limit proxy egress to internal systems wherever business requirements allow.
Prioritize systems processing untrusted or user-supplied URLs.
Validation and detection
Inventory OpenClaw versions and flag anything before 2026.3.2.
Inspect runtime environments for HTTP_PROXY, HTTPS_PROXY, and ALL_PROXY.
Identify OpenClaw features using web_fetch or strict URL fetch paths.
Review whether low-privileged users can influence fetched URLs.
Confirm upgraded builds include the referenced patch or fixed release.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.