Is github.com/gin-contrib/cors 1.5 vulnerable?

Go · 1 release from 1.5.0 to 1.5.0 · latest github.com/gin-contrib/cors is 1.7.11 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. github.com/gin-contrib/cors 1.5.0, the last 1.5 release, is affected by 2 known security advisories (1 critical, 1 low), including CVE-2019-25211, CVE-2019-25211. Upgrade to 1.6.0 or later to fix all of them.

Upgrade with:go get github.com/gin-contrib/cors@v1.6.0

Is your project on an affected github.com/gin-contrib/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/gin-contrib/cors 1.5.0

  • LowCVE-2019-25211GO-2024-29552 Jul 2024

    Gin mishandles a wildcard in the origin string in github.com/gin-contrib/cors

    Affected
    <1.6.0
    Fixed in
    1.6.0
  • CriticalCVE-2019-25211GHSA-869c-j7wc-8jqv29 Jun 2024

    Gin mishandles a wildcard at the end of an origin string

    Affected
    <1.6.0
    Fixed in
    1.6.0

Which of your client projects are still on github.com/gin-contrib/cors 1.5?

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

Other github.com/gin-contrib/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.