Is sweetalert2 10.16 vulnerable?

npm · 12 releases from 10.16.0 to 10.16.11 · latest sweetalert2 is 11.26.25 · checked 2 Nov 2026

Yes: 3 known advisories

Yes. sweetalert2 10.16.11, the last 10.16 release, is affected by 3 known security advisories (3 low). Upgrade to 11.22.4 or later to fix all of them.

Upgrade with:npm install sweetalert2@11.22.4

Is your project affected?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Advisories affecting sweetalert2 10.16.11

  • LowGHSA-8jh9-wqpf-q52c23 Nov 2022

    sweetalert2 v8.19.1 and above contains hidden functionality

    Affected
    >=8.19.1 <11.22.4
    Fixed in
    11.22.4
  • LowGHSA-pg98-6v7f-2xfv23 Nov 2022

    sweetalert2 v9.17.4 and above contains hidden functionality

    Affected
    >=9.17.4 <11.22.4
    Fixed in
    11.22.4
  • LowGHSA-457r-cqc8-9vj923 Nov 2022

    sweetalert2 v10.16.10 and above contains hidden functionality

    Affected
    >=10.16.10 <11.22.4
    Fixed in
    11.22.4

Which of your client projects are still on sweetalert2 10.16?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact sweetalert2 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other sweetalert2 versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.