https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 19:38:11 +0000 https://vulnerability.circl.lu/vuln/cve-2026-32913 <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.3.7 contains an improper header validation vulnerability in fetchWithSsrFGuard that forwards custom authorization headers across cross-origin redirects. Attackers can trigger redirects to different origins to intercept sensitive headers like X-Api-Key and Private-Token intended for the original destination.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw before 2026.3.7 contains an improper header validation vulnerability in fetchWithSsrFGuard that forwards custom authorization headers across cross-origin redirects. Attackers can trigger redirects to different origins to intercept sensitive headers like X-Api-Key and Private-Token intended for the original destination.</p> https://vulnerability.circl.lu/vuln/cve-2026-32913 https://vulnerability.circl.lu/vuln/ghsa-6mgf-v5j7-45cr <p><strong>Affected:</strong> npm: openclaw</p> <p>OpenClaw&#39;s `fetchWithSsrFGuard(...)` followed cross-origin redirects while preserving arbitrary caller-supplied headers except for a narrow denylist (`Authorization`, `Proxy-Authorization`, `Cookie`, `Cookie2`). This allowed custom authorization headers such as `X-Api-Key`, `Private-Token`, and similar sensitive headers to be forwarded to a different origin after a redirect.</p> <p>The fix switches cross-origin redirect handling from a narrow sensitive-header denylist to a safe-header allowlist, so only benign headers such as content negotiation and cache validators survive an origin change.</p> <p>## Affected Packages / Versions</p> <p>- Package: `openclaw` (npm) - Affected versions: `&lt;= 2026.3.2` - Patched version: `2026.3.7` - Latest published npm version at patch time: `2026.3.2`</p> <p>## Impact</p> <p>A remote service that could trigger a redirect across origins could receive custom authorization credentials attached by OpenClaw callers. This can expose API keys, bearer-style custom headers, or private token headers intended only for the original destination.</p> <p>## Fix Commit(s)</p> <p>- `46715371b0612a6f9114dffd1466941ac476cef5`</p> <p>## Verification</p> <p>- `pnpm check` passed - `pnpm test:fast` passed - Focused redirect regression tests passed - `pnpm exec vitest run --config vitest.gateway.config.ts` still has unrelated current-`main` failures in `src/gateway/server-channels.test.ts` and `src/gateway/server-methods/agents-mutate.test.ts`</p> <p>## Release Process Note</p> <p>npm `2026.3.7` was published on March 8, 2026. Th…</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>OpenClaw&#39;s `fetchWithSsrFGuard(...)` followed cross-origin redirects while preserving arbitrary caller-supplied headers except for a narrow denylist (`Authorization`, `Proxy-Authorization`, `Cookie`, `Cookie2`). This allowed custom authorization headers such as `X-Api-Key`, `Private-Token`, and similar sensitive headers to be forwarded to a different origin after a redirect.</p> <p>The fix switches cross-origin redirect handling from a narrow sensitive-header denylist to a safe-header allowlist, so only benign headers such as content negotiation and cache validators survive an origin change.</p> <p>## Affected Packages / Versions</p> <p>- Package: `openclaw` (npm) - Affected versions: `&lt;= 2026.3.2` - Patched version: `2026.3.7` - Latest published npm version at patch time: `2026.3.2`</p> <p>## Impact</p> <p>A remote service that could trigger a redirect across origins could receive custom authorization credentials attached by OpenClaw callers. This can expose API keys, bearer-style custom headers, or private token headers intended only for the original destination.</p> <p>## Fix Commit(s)</p> <p>- `46715371b0612a6f9114dffd1466941ac476cef5`</p> <p>## Verification</p> <p>- `pnpm check` passed - `pnpm test:fast` passed - Focused redirect regression tests passed - `pnpm exec vitest run --config vitest.gateway.config.ts` still has unrelated current-`main` failures in `src/gateway/server-channels.test.ts` and `src/gateway/server-methods/agents-mutate.test.ts`</p> <p>## Release Process Note</p> <p>npm `2026.3.7` was published on March 8, 2026. Th…</p> https://vulnerability.circl.lu/vuln/ghsa-6mgf-v5j7-45cr