Go to packages list

sentry-nextjs

Ecosystem: npm

Downloads: 54.35 Mln

Vulnerabilities from the last (months)
  • 1CriticalAffects 3 versions
  • 0HighAffects 0 versions
  • 0MediumAffects 0 versions
  • 2ModerateAffects 2 versions
  • 1LowAffects 1 version
Severity distribution (all time)
4vulnerabilities
  • Critical1 (25.0%)
  • High0 (0.0%)
  • Medium0 (0.0%)
  • Moderate2 (50.0%)
  • Low1 (25.0%)

Monthly breakdown

  • Critical
  • High
  • Medium
  • Moderate
  • Low
  • 1 vulnerabilities
    • Critical: 1
    • High: 0
    • Medium: 0
    • Moderate: 0
    • Low: 0
  • 1 vulnerabilities
    • Critical: 0
    • High: 0
    • Medium: 0
    • Moderate: 1
    • Low: 0
  • 1 vulnerabilities
    • Critical: 0
    • High: 0
    • Medium: 0
    • Moderate: 0
    • Low: 1
  • 1 vulnerabilities
    • Critical: 0
    • High: 0
    • Medium: 0
    • Moderate: 1
    • Low: 0

Vulnerabilities (4)

Known vulnerabilities affecting sentry-nextjs, based on data from OSV.

Vulnerabilities affecting sentry-nextjs
IDSeveritySummaryAffected versionsPublishedSource
GHSA-mchm-gjx6-7h55CriticalSentry-Javascript: Middleware Bypass when using Tunnel route### Impact The `tunnelRoute` option makes the SDK send browser events to a path on your own Next.js server (for example `/monitoring`), where a rewrite forwards them to Sentry to prevent ad blockers from blocking them. To keep those envelope requests from being rejected by your middleware, the SDK skips middleware for them. The middleware skip was wider than the rewrite. The rewrite only serves requests to the tunnel path itself with the `o` and `p` parameters set. The skip applied to anything under the tunnel path. Requests in that gap go to your application instead of Sentry, and your midd
  • >= 9.36.0, < 9.47.2
  • >= 10.0.0-alpha.0, < 10.75.2
  • >= 11.0.0-alpha.0, < 11.0.0-rc.1
GitHub (opens in a new tab)
GHSA-6465-jgvq-jhgpModerateSentry's sensitive headers are leaked when `sendDefaultPii` is set to `true`### Impact In version 10.11.0, a change to how the SDK collects request data in Node.js applications caused certain incoming HTTP headers to be added as trace span attributes. When `sendDefaultPii: true` was set, a few headers that were previously redacted - including Authorization and Cookie - were unintentionally allowed through. Sentry’s server-side scrubbing (handled by Sentry's Relay edge proxy) normally serves as a second layer of protection. However, because it relied on the same matching logic as the SDK, it also failed to catch these headers in this case. Users may be impacted if:
  • >= 10.11.0, < 10.27.0
GitHub (opens in a new tab)
GHSA-r5w7-f542-q2j4LowPotential DoS when using ContextLines integration### Impact The [ContextLines integration](https://docs.sentry.io/platforms/javascript/guides/node/configuration/integrations/contextlines/) uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events. The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS). The ContextLines integration is enabled by default in the Node SDK (`@sentry/node`) and SDKs that run in Node.js environments (`@sen
  • >= 8.10.0, < 8.49.0
GitHub (opens in a new tab)
GHSA-2rmr-xw8m-22q9ModerateSentry Next.js vulnerable to SSRF via Next.js SDK tunnel endpoint### Impact An unsanitized input of Next.js SDK tunnel endpoint allows sending HTTP requests to arbitrary URLs and reflecting the response back to the user. This could open door for other attack vectors: * client-side vulnerabilities: XSS/CSRF in the context of the trusted domain; * interaction with internal network; * read cloud metadata endpoints (AWS, Azure, Google Cloud, etc.); * local/remote port scan. This issue only affects users who have [Next.js SDK tunneling feature](https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#configure-tunneling-to-avoid-ad-blockers) enab
  • >= 7.26.0, < 7.77.0
GitHub (opens in a new tab)
  • GHSA-mchm-gjx6-7h55Critical
    Sentry-Javascript: Middleware Bypass when using Tunnel route
    • >= 9.36.0, < 9.47.2
    • >= 10.0.0-alpha.0, < 10.75.2
    • +1 more
    GitHub (opens in a new tab)
    Affected versions:
    • >= 9.36.0, < 9.47.2
    • >= 10.0.0-alpha.0, < 10.75.2
    • >= 11.0.0-alpha.0, < 11.0.0-rc.1

    ### Impact The `tunnelRoute` option makes the SDK send browser events to a path on your own Next.js server (for example `/monitoring`), where a rewrite forwards them to Sentry to prevent ad blockers from blocking them. To keep those envelope requests from being rejected by your middleware, the SDK skips middleware for them. The middleware skip was wider than the rewrite. The rewrite only serves requests to the tunnel path itself with the `o` and `p` parameters set. The skip applied to anything under the tunnel path. Requests in that gap go to your application instead of Sentry, and your midd

    CVE: CVE-2026-114139

  • GHSA-6465-jgvq-jhgpModerate
    Sentry's sensitive headers are leaked when `sendDefaultPii` is set to `true`
    • >= 10.11.0, < 10.27.0
    GitHub (opens in a new tab)

    ### Impact In version 10.11.0, a change to how the SDK collects request data in Node.js applications caused certain incoming HTTP headers to be added as trace span attributes. When `sendDefaultPii: true` was set, a few headers that were previously redacted - including Authorization and Cookie - were unintentionally allowed through. Sentry’s server-side scrubbing (handled by Sentry's Relay edge proxy) normally serves as a second layer of protection. However, because it relied on the same matching logic as the SDK, it also failed to catch these headers in this case. Users may be impacted if:

    CVE: CVE-2025-65944

  • GHSA-r5w7-f542-q2j4Low
    Potential DoS when using ContextLines integration
    • >= 8.10.0, < 8.49.0
    GitHub (opens in a new tab)

    ### Impact The [ContextLines integration](https://docs.sentry.io/platforms/javascript/guides/node/configuration/integrations/contextlines/) uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events. The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS). The ContextLines integration is enabled by default in the Node SDK (`@sentry/node`) and SDKs that run in Node.js environments (`@sen

  • GHSA-2rmr-xw8m-22q9Moderate
    Sentry Next.js vulnerable to SSRF via Next.js SDK tunnel endpoint
    • >= 7.26.0, < 7.77.0
    GitHub (opens in a new tab)

    ### Impact An unsanitized input of Next.js SDK tunnel endpoint allows sending HTTP requests to arbitrary URLs and reflecting the response back to the user. This could open door for other attack vectors: * client-side vulnerabilities: XSS/CSRF in the context of the trusted domain; * interaction with internal network; * read cloud metadata endpoints (AWS, Azure, Google Cloud, etc.); * local/remote port scan. This issue only affects users who have [Next.js SDK tunneling feature](https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#configure-tunneling-to-avoid-ad-blockers) enab

    CVE: CVE-2023-46729

Showing 1-4 of 4 vulnerabilities