Is github.com/rs/cors 1.3 vulnerable?

Go · 1 release from 1.3.0 to 1.3.0 · latest github.com/rs/cors is 1.11.1 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. github.com/rs/cors 1.3.0, the last 1.3 release, is affected by 2 known security advisories (1 medium, 1 low), including CVE-2018-20744, CVE-2018-20744. Upgrade to 1.5.0 or later to fix all of them.

Upgrade with:go get github.com/rs/cors@v1.5.0

Is your project on an affected github.com/rs/cors?

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/rs/cors 1.3.0

  • LowCVE-2018-20744GO-2023-17928 Jun 2023

    Insecure wildcard CORS policy in github.com/rs/cors

    Affected
    <1.5.0
    Fixed in
    1.5.0
  • MediumCVE-2018-20744GHSA-927h-x4qj-r24214 May 2022

    github.com/gofiber/fiber/v2 vulnerable to Origin Validation Error

    Affected
    <1.5.0
    Fixed in
    1.5.0

Which of your client projects are still on github.com/rs/cors 1.3?

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

Other github.com/rs/cors 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.