Is github.com/alist-org/alist/v3 3.55 vulnerable?

Go · 1 release from 3.55.0 to 3.55.0 · latest github.com/alist-org/alist/v3 is 3.66.0 · checked 18 Nov 2026

Yes: 4 known advisories

Yes. github.com/alist-org/alist/v3 3.55.0, the last 3.55 release, is affected by 4 known security advisories (1 critical, 1 high, 2 low), including CVE-2026-25160, CVE-2026-25161, CVE-2026-25160. Upgrade to 3.57.0 or later to fix all of them.

Upgrade with:go get github.com/alist-org/alist/v3@v3.57.0

Is your project on an affected github.com/alist-org/alist/v3?

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

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting github.com/alist-org/alist/v3 3.55.0

  • LowCVE-2026-25160GO-2026-44145 Feb 2026

    Alist has Insecure TLS Config in github.com/alist-org/alist

    Affected
    <3.57.0
    Fixed in
    3.57.0
  • LowCVE-2026-25161GO-2026-44155 Feb 2026

    Alist vulnerable to Path Traversal in multiple file operation handlers in github.com/alist-org/alist

    Affected
    <3.57.0
    Fixed in
    3.57.0
  • HighCVE-2026-25161GHSA-x4q4-7phh-42j94 Feb 2026

    Alist vulnerable to Path Traversal in multiple file operation handlers

    Affected
    <3.57.0
    Fixed in
    3.57.0
  • CriticalCVE-2026-25160GHSA-8jmm-3xwx-w9744 Feb 2026

    Alist has Insecure TLS Config

    Affected
    <3.57.0
    Fixed in
    3.57.0

Which of your client projects are still on github.com/alist-org/alist/v3 3.55?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/alist-org/alist/v3 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other github.com/alist-org/alist/v3 versions

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