Enforce configured CORS origins#237
Merged
Merged
Conversation
Use the explicit CORS origin configuration for credentialed browser requests and reject unconfigured cross-origin callers.
coder13
force-pushed
the
agent/cors-allowlist
branch
from
July 14, 2026 03:32
6ffdc72 to
b59d5a9
Compare
coder13
marked this pull request as ready for review
July 14, 2026 03:34
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
The server previously reflected every caller origin while allowing credentials. That allowed any website to make credentialed cross-origin requests.
User impact
Configured production and local development origins continue to work. Unconfigured cross-origin callers no longer receive CORS permission. No email-related behavior is added or changed.
Validation
Closes #236.