Greptile Summary

This PR adds documentation to SECURITY.md clarifying the SSRF reporting scope for the operator-managed HTTP/WebSocket proxy-routing feature introduced in #70044. It adds a new dedicated section, a matching false-positive pattern bullet, and an out-of-scope bullet — all consistent with each other and with the referenced implementation (fetchWithSsrFGuard, proxy.enabled, etc., verified against the codebase).

Confidence Score: 5/5

Safe to merge — docs-only change with no code impact.

Purely documentation. The three added blocks (false-positive bullet, new section, out-of-scope bullet) are internally consistent and match verified codebase identifiers (fetchWithSsrFGuard, proxy.enabled, OPENCLAW_PROXY_URL). No logic, security boundaries, or runtime behavior are modified.

No files require special attention.

_{Reviews (1): Last reviewed commit: "docs(security): clarify proxy SSRF repor..." | Re-trigger Greptile}

Codex review: needs maintainer review before merge.

What this changes:

This PR updates SECURITY.md with SSRF triage scope for operator-managed HTTP/WebSocket proxy routing, revises docs/security/network-proxy.md wording around proxy guardrails, and adds a CHANGELOG.md entry for the merged media decode triage-policy change in #74311.

Maintainer follow-up before merge:

Protected maintainer-labeled security-policy documentation PR needs human maintainer/security review and normal exact-head validation, not an automated replacement or repair PR.

Best possible solution:

The durable end state should be public SECURITY.md and Network proxy docs that give researchers a precise HTTP/WebSocket proxy-routing triage boundary while leaving non-HTTP egress and unrelated features assessed separately.

Acceptance criteria:

• Review rendered SECURITY.md and https://docs.openclaw.ai/security/network-proxy wording for proxy SSRF triage scope and overbreadth.
• Run or confirm exact-head docs formatting for CHANGELOG.md SECURITY.md docs/security/network-proxy.md.
• Confirm exact-head CI/docs checks before landing.

What I checked:

• protected-maintainer-pr: Provided PR metadata shows authorAssociation MEMBER and label maintainer, which the cleanup policy keeps open for explicit maintainer handling. (bcb60c07a12e)
• main-missing-security-proxy-scope: Current main's SECURITY.md false-positive and out-of-scope sections do not contain the proposed operator-managed HTTP/WebSocket proxy-routing SSRF bullets. (SECURITY.md:66, a972c9ec4547)
• main-still-has-guarded-fetch-wording: Current network proxy docs still say the proxy is additional to application-level SSRF guards such as fetchWithSsrFGuard, and the limits section still says it does not replace fetchWithSsrFGuard; those are the docs lines this PR changes. Public docs: docs/security/network-proxy.md. (docs/security/network-proxy.md:26, a972c9ec4547)
• current-proxy-boundary-docs: Current docs define the proxy as optional operator-managed routing for normal process-local HTTP/WebSocket clients, state OpenClaw does not certify the proxy, and list raw sockets/native addons/child processes as limits. Public docs: docs/security/network-proxy.md. (docs/security/network-proxy.md:11, a972c9ec4547)
• current-proxy-source-boundary: Current proxy lifecycle code resolves proxy.proxyUrl or OPENCLAW_PROXY_URL, accepts only http:// proxy URLs, fails startup when enabled without a valid URL, injects proxy environment/global-agent state, clears NO_PROXY-style bypass env vars, and limits the Gateway control-plane bypass to loopback URLs. (src/infra/net/proxy/proxy-lifecycle.ts:319, a972c9ec4547)
• current-proxy-coverage: Existing e2e coverage routes fetch, node:http, explicit HTTP agents, HTTPS CONNECT, and WebSocket traffic through the operator-managed proxy while confirming the loopback Gateway bypass remains narrow. (src/infra/net/proxy/external-proxy.e2e.test.ts:177, a972c9ec4547)

Likely related people:

• jesse-merhi: Provided related context shows @jesse-merhi authored the merged operator-managed network proxy routing work in feat(security): support operator-managed network proxy routing #70044, and current CHANGELOG.md credits them for that feature; this PR documents that feature boundary. (role: introduced behavior and likely domain owner; confidence: high; commits: 2633b1491413; files: src/infra/net/proxy/proxy-lifecycle.ts, src/infra/net/proxy/external-proxy.e2e.test.ts, docs/security/network-proxy.md)
• steipete: Local history shows Peter Steinberger authored the merged docs: classify media decode overhead as performance-only #74311 SECURITY.md triage-policy change that this PR references for the changelog entry, and recent SECURITY.md policy edits are the surface being updated. (role: recent adjacent maintainer and security-policy maintainer; confidence: medium; commits: abaa4326d81b; files: SECURITY.md, CHANGELOG.md)
• joshavant: Current CHANGELOG.md credits @joshavant alongside @jesse-merhi for feat(security): support operator-managed network proxy routing #70044, the operator-managed proxy routing feature whose security-reporting boundary this PR clarifies. (role: adjacent proxy feature context; confidence: medium; commits: 2633b1491413; files: src/infra/net/proxy/proxy-lifecycle.ts, docs/security/network-proxy.md)

Remaining risk / open question:

• The proposed SECURITY.md wording is security-policy triage language; maintainers should confirm it does not over-scope non-HTTP/WebSocket egress, raw sockets, native addons, child processes, or unrelated SSRF reports.

Codex review notes: model gpt-5.5, reasoning high; reviewed against a972c9ec4547.

Merged via squash.

• Prepared head SHA: 7dd9fcfade491741e405eec06ab9d235c47bfc26
• Merge commit: 542821cd1e60e34caec7df84f8583007b5b98f63

Thanks @jesse-merhi!