Stop exposing exception details in HTTP responses#5903
Merged
Conversation
Addresses CodeQL "Information exposure through an exception" findings in views/subscription.py and viewsets/channel.py. Logs the traceback server side via logger.exception so Sentry still captures it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
marcellamaki
approved these changes
May 13, 2026
Member
marcellamaki
left a comment
marcellamaki
left a comment
There was a problem hiding this comment.
This seems to match the recommendation from the CodeQL checks on the release PR
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
3 participants
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
Replaces
str(exception)in HTTP error responses with generic messages and switches the correspondinglogger.errorcalls tologger.exceptionso the traceback is still captured by Sentry. Addresses three CodeQL "Information exposure through an exception" findings flagged on PR #5902:views/subscription.py:84(Stripe checkout session)views/subscription.py:110(Stripe customer portal session)viewsets/channel.py:472(channelIntegrityErroron create)References
Reviewer guidance
useSubscription.js) only checkserrortruthiness, so the generic responses don't change user-facing UX.AI usage
Used Claude Code to identify the three CodeQL findings, apply the fixes, and verify the frontend doesn't depend on the exception text in the response body.