How severe is GHSA-457r-cqc8-9vj9?

No CVSS score has been assigned to GHSA-457r-cqc8-9vj9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-457r-cqc8-9vj9?

GHSA-457r-cqc8-9vj9 affects the following packages: sweetalert2 (npm). Ecosystems affected: npm.

How do I fix GHSA-457r-cqc8-9vj9?

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

How do I detect GHSA-457r-cqc8-9vj9 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sweetalert2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-457r-cqc8-9vj9 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-457r-cqc8-9vj9?

O3 pinpoints whether GHSA-457r-cqc8-9vj9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-457r-cqc8-9vj9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-457r-cqc8-9vj9 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-457r-cqc8-9vj9 published, and has it been updated?

GHSA-457r-cqc8-9vj9 was published on November 23, 2022 and was last updated on August 25, 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

GHSA-457r-cqc8-9vj9

GHSA-457r-cqc8-9vj9 is a security vulnerability in sweetalert2. O3 Security confirms whether GHSA-457r-cqc8-9vj9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

sweetalert2 v10.16.10 and above contains hidden functionality

Published

Nov 23, 2022

Updated

Aug 25, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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.

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

sweetalert2npm

1.0Mdownloads / week

Description

sweetalert2 versions 10.16.10 and up until 11.0.0 are vulnerable to hidden functionality that was introduced by the maintainer. The package outputs audio and/or video messages that do not pertain to the functionality of the package and is not included in versions 10.0.0 - 10.16.9.

Workaround

Use a version 10.0.0 - 10.16.9 of the package until the maintainer releases a fix.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`sweetalert2`	≥ 10.16.10&&< 11.22.4	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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update sweetalert2 to 11.22.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-457r-cqc8-9vj9 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 pinpoints whether GHSA-457r-cqc8-9vj9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-457r-cqc8-9vj9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`sweetalert2` versions 10.16.10 and up until 11.0.0 are vulnerable to hidden functionality that was introduced by the maintainer. The package outputs audio and/or video messages that do not pertain to the functionality of the package and is not included in versions 10.0.0 - 10.16.9. ### Workaround Use a version 10.0.0 - 10.16.9 of the package until the maintainer releases a fix.

O3 Security · Impact-Aware SCA

Is GHSA-457r-cqc8-9vj9 in your dependencies?

O3 detects GHSA-457r-cqc8-9vj9 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works