Skip to content

fix(realm): allow the AI assistant CDN and the hydration script in the CSP #394

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
h0pped merged 2 commits into from
Aug 20, 2026
Merged

fix(realm): allow the AI assistant CDN and the hydration script in the CSP #394

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c4c1731
fix(realm): allow the AI assistant CDN and the hydration script in th…
h0pped Aug 20, 2026
1375a3e
Merge branch 'main' into fix/csp-allow-ai-assistant-cdn
h0pped Aug 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion redocly.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -205,6 +205,7 @@ responseHeaders:
https://js.hs-analytics.net
https://js.hs-banner.com
https://cdn.jsdelivr.net
https://cdn.redocly.com

@redocly redocly Bot Aug 20, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Severity: Low

Allowing the entire https://cdn.redocly.com domain in script-src is broader than necessary. Consider using a more restrictive path (e.g., https://cdn.redocly.com/ai-assistant/) to minimize the attack surface while still enabling the widget.

'sha256-M28mypAFwwpIwIF9e1/A6867PQiwVvOrdqFSTFSa8/U='
'sha256-Ed6Lei7deBSXT1iYYw0V36YZXaA4v7OsRknNjmNl/9c='
'sha256-uDN+KkW4ljf+D4DbsWP5KpxyfG/7h+LNmZxMzbz/+1E='
Expand All @@ -220,7 +221,8 @@ responseHeaders:
'sha256-+Ozb/ItuZAdaQgJd2RebN2rKWj1XkBuXVaV6/lT4Juo='
'sha256-9qgU5FDrauEgF+e1iJWvsh46OwsIkNOLjkXggr/02jk='
'sha256-v7ddZtWCUr5oF3kgrlEot4fG861CKDXUt0aTaNaIk6Q='
'sha256-+t5Z3fJi7uJxARWEzFEVaSRgtaAn0r97XkxpJNbQiK0=';
'sha256-+t5Z3fJi7uJxARWEzFEVaSRgtaAn0r97XkxpJNbQiK0='
'sha256-gOx3nRh8znDQR7T1VkI+fFXDgsNzf5enQqdi7NP11Vk=';

@redocly redocly Bot Aug 20, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Severity: Medium

The React hydration script will remain blocked on /editor because its route-specific block replaces the global CSP. Add the new hydration script hash to the /editor block to resolve the hydration error there as well.

@redocly redocly Bot Aug 20, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Severity: Low

The hash for window.__staticRouterHydrationData may be brittle. Since hydration data typically varies by route, a single static hash in the global CSP might only resolve violations for specific pages, leaving hydration errors elsewhere.

object-src 'none';
base-uri 'self';
connect-src
Expand Down
Loading