How severe is GHSA-8jh9-wqpf-q52c?

No CVSS score has been assigned to GHSA-8jh9-wqpf-q52c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8jh9-wqpf-q52c?

GHSA-8jh9-wqpf-q52c affects the following packages: sweetalert2 (npm). Ecosystems affected: npm.

How do I fix GHSA-8jh9-wqpf-q52c?

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

How do I detect GHSA-8jh9-wqpf-q52c 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-8jh9-wqpf-q52c 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-8jh9-wqpf-q52c?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-8jh9-wqpf-q52c can be triaged on real exposure rather than presence alone.

Is GHSA-8jh9-wqpf-q52c actively exploited in the wild?

No public exploit code has been indexed for GHSA-8jh9-wqpf-q52c 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-8jh9-wqpf-q52c published, and has it been updated?

GHSA-8jh9-wqpf-q52c was published on November 23, 2022 and was last updated on September 24, 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

GHSA-8jh9-wqpf-q52c — sweetalert2

GHSA-8jh9-wqpf-q52c is a security vulnerability in sweetalert2. A fix is available for sweetalert2 — see the affected versions and patch details below.

sweetalert2 v8.19.1 and above contains hidden functionality

Published

Nov 23, 2022

Updated

Sep 24, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 24, 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

672Kdownloads / week

Description

sweetalert2 versions 8.19.1 and up until 9.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 below 8.19.1.

Workaround

Users who are unable to update to the fixed version (11.22.4) can use package versions 8.19.0 and below, as they do not contain the hidden functionality.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`sweetalert2`	≥ 8.19.1&&< 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-8jh9-wqpf-q52c 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-8jh9-wqpf-q52c can be triaged on real exposure rather than presence alone.

Tailored to GHSA-8jh9-wqpf-q52c. 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 8.19.1 and up until 9.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 below 8.19.1. ### Workaround Users who are unable to update to the fixed version (11.22.4) can use package versions 8.19.0 and below, as they do not contain the hidden functionality.

O3 Security · Impact-Aware SCA

Is GHSA-8jh9-wqpf-q52c in your dependencies?

O3 Security finds GHSA-8jh9-wqpf-q52c 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