How severe is GHSA-593m-55hh-j8gv?

GHSA-593m-55hh-j8gv has a CVSS score of 5.6/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-593m-55hh-j8gv?

GHSA-593m-55hh-j8gv affects the following packages: @sentry/browser (npm), @sentry/browser (npm). Ecosystems affected: npm.

How do I fix GHSA-593m-55hh-j8gv?

Update @sentry/browser to 8.33.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-593m-55hh-j8gv is resolved across your whole dependency graph.

How do I detect GHSA-593m-55hh-j8gv in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sentry/browser, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-593m-55hh-j8gv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-593m-55hh-j8gv?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-593m-55hh-j8gv can be triaged on real exposure rather than presence alone.

Is GHSA-593m-55hh-j8gv actively exploited in the wild?

No public exploit code has been indexed for GHSA-593m-55hh-j8gv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-593m-55hh-j8gv published, and has it been updated?

GHSA-593m-55hh-j8gv was published on October 3, 2024 and was last updated on October 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

GHSA-593m-55hh-j8gv — @sentry/browser

MEDIUMFix: getsentry/sentry-javascript#13838

GHSA-593m-55hh-j8gv is a medium-severity (CVSS 5.6) vulnerability in @sentry/browser. A fix is available for @sentry/browser — see the affected versions and patch details below.

Sentry SDK Prototype Pollution gadget in JavaScript SDKs

Published

Oct 3, 2024

Updated

Oct 4, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 4, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@sentry/browsernpm

24.0Mdownloads / week

Description

Impact

In case a Prototype Pollution vulnerability is present in a user's application or bundled libraries, the Sentry SDK could potentially serve as a gadget to exploit that vulnerability. The exploitability depends on the specific details of the underlying Prototype Pollution issue.

[!NOTE] This advisory does not indicate the presence of a Prototype Pollution within the Sentry SDK itself. Users are strongly advised to first address any Prototype Pollution vulnerabilities in their application, as they pose a more critical security risk.

Patches

The issue was patched in all Sentry JavaScript SDKs starting from the 8.33.0 version. Also, the fix was backported to SDK v7 in 7.119.1.

References

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@sentry/browser`	≥ 8.0.0-alpha.1&&< 8.33.0	8.33.0`npm install @sentry/browser@8.33.0`
📦npm	`@sentry/browser`	all versions	7.119.1`npm install @sentry/browser@7.119.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sentry/browser, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @sentry/browser to 8.33.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-593m-55hh-j8gv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-593m-55hh-j8gv can be triaged on real exposure rather than presence alone.

Tailored to GHSA-593m-55hh-j8gv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact In case a Prototype Pollution vulnerability is present in a user's application or bundled libraries, the Sentry SDK could potentially serve as a gadget to exploit that vulnerability. The exploitability depends on the specific details of the underlying Prototype Pollution issue. > [!NOTE] > This advisory does not indicate the presence of a Prototype Pollution within the Sentry SDK itself. Users are strongly advised to first address any Prototype Pollution vulnerabilities in their application, as they pose a more critical security risk. ### Patches The issue was patched in all Sentr

O3 Security · Impact-Aware SCA

Is GHSA-593m-55hh-j8gv in your dependencies?

O3 Security finds GHSA-593m-55hh-j8gv across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works