Skip to content

Sensitive URL query params leak to Sentry in transaction events #25247

Closed

Description

@mfb

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/browser

SDK Version

10.76.2

Framework Version

No response

Link to Sentry event

No response

Reproduction Example/SDK Setup

I set the tracesSampleRate to 1, and dataCollection.userInfo to false; otherwise didn't configure dataCollection.

Steps to Reproduce

Load a page with a sensitive URL query param, such as "?jwt=baz", and analyze the transaction event sent to Sentry.

Expected Result

I would have assumed that the sensitive query param would be filtered.

Actual Result

The value of the sensitive query param is sent to Sentry in span descriptions as well as the transaction's request.url property.

Additional Context

I believe this does work correctly on the 11.x branch; this is a bug report for the 10.x branch.

Priority

No response

Activity

  1. linear-code commented on Oct 12, 2026

    @linear-code
  2. self-assigned this
    on Oct 12, 2026
  3. JPeer264 commented on Oct 12, 2026

    @JPeer264
    Member

    Thanks for raising this. This might have been something we missed here. I'm on it.

    FWIW it would be dataCollection.urlQueryParams that should filter these

  4. added a commit that references this issue on Oct 12, 2026
    ee04661
  5. github-actions commented on Oct 12, 2026

    @github-actions
    Contributor

    A PR closing this issue has just been released 🚀

    This issue was referenced by PR #25262, which was included in the 11.7.0 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BrowserBugjavascriptPull requests that update javascript code

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions