How severe is GHSA-mrr8-v49w-3333?

No CVSS score has been assigned to GHSA-mrr8-v49w-3333 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mrr8-v49w-3333?

GHSA-mrr8-v49w-3333 affects the following packages: sweetalert2 (npm). Ecosystems affected: npm.

How do I fix GHSA-mrr8-v49w-3333?

Update sweetalert2 to 11.22.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mrr8-v49w-3333 is resolved across your whole dependency graph.

How do I detect GHSA-mrr8-v49w-3333 in my npm dependencies?

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

How do I mitigate GHSA-mrr8-v49w-3333 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.

Is GHSA-mrr8-v49w-3333 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mrr8-v49w-3333 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-mrr8-v49w-3333 published, and has it been updated?

GHSA-mrr8-v49w-3333 was published on July 10, 2023 and was last updated on August 14, 2025. 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

sweetalert2 contains potentially undesirable behaviorGHSA-mrr8-v49w-3333

Fix: sweetalert2/sweetalert2#2847

GHSA-mrr8-v49w-3333 is a security vulnerability in sweetalert2. A fix is available for sweetalert2 — see the affected versions and patch details below.

Published

Jul 10, 2023

Updated

Aug 14, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 14, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg 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.

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

sweetalert2npm

1.3Mdownloads / week

Description

sweetalert2 versions from 11.6.14 to before 11.22.4 have potentially undesirable behavior. The package outputs audio and/or video messages that do not pertain to the functionality of the package when run on specific tlds. This functionality is documented on the project's readme.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`sweetalert2`	≥ 11.6.14&&< 11.22.4	11.22.4`npm install sweetalert2@11.22.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sweetalert2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sweetalert2 to 11.22.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mrr8-v49w-3333 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.

Frequently Asked Questions

`sweetalert2` versions from 11.6.14 to before 11.22.4 have potentially undesirable behavior. The package outputs audio and/or video messages that do not pertain to the functionality of the package when run on specific tlds. This functionality is documented on the project's readme.

O3 Security · Impact-Aware SCA

Is GHSA-mrr8-v49w-3333 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works