How severe is GHSA-qq6h-5g6j-q3cm?

No CVSS score has been assigned to GHSA-qq6h-5g6j-q3cm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qq6h-5g6j-q3cm?

GHSA-qq6h-5g6j-q3cm affects the following packages: sweetalert2 (npm). Ecosystems affected: npm.

How do I fix GHSA-qq6h-5g6j-q3cm?

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

How do I detect GHSA-qq6h-5g6j-q3cm 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-qq6h-5g6j-q3cm 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-qq6h-5g6j-q3cm?

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

Is GHSA-qq6h-5g6j-q3cm actively exploited in the wild?

No public exploit code has been indexed for GHSA-qq6h-5g6j-q3cm 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-qq6h-5g6j-q3cm published, and has it been updated?

GHSA-qq6h-5g6j-q3cm 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

Not in CISA KEV

GHSA-qq6h-5g6j-q3cm — sweetalert2

GHSA-qq6h-5g6j-q3cm is a security vulnerability in sweetalert2. A fix is available for sweetalert2 — see the affected versions and patch details below.

sweetalert2 v11.4.9 and above contains hidden functionality

Published

Nov 23, 2022

Updated

Aug 25, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 25, 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

712Kdownloads / week

Description

sweetalert2 versions 11.4.9 and above 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 11.0.0 - 11.4.8.

Workaround

Use a version 11.0.0 - 11.4.8 of the package until the maintainer releases a fix.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`sweetalert2`	≥ 11.4.9&&< 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-qq6h-5g6j-q3cm 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-qq6h-5g6j-q3cm can be triaged on real exposure rather than presence alone.

Tailored to GHSA-qq6h-5g6j-q3cm. 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 11.4.9 and above 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 11.0.0 - 11.4.8. ### Workaround Use a version 11.0.0 - 11.4.8 of the package until the maintainer releases a fix.

O3 Security · Impact-Aware SCA

Is GHSA-qq6h-5g6j-q3cm in your dependencies?

O3 Security finds GHSA-qq6h-5g6j-q3cm 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