Is github.com/gin-contrib/cors 1.3 vulnerable?
Go · 2 releases from 1.3.0 to 1.3.1 · 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.3.1, the last 1.3 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.
go get github.com/gin-contrib/cors@v1.6.0Is your project on an affected github.com/gin-contrib/cors?
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.3.1
Gin mishandles a wildcard in the origin string in github.com/gin-contrib/cors
- Affected
- <1.6.0
- Fixed in
- 1.6.0
Gin mishandles a wildcard at the end of an origin string
- Affected
- <1.6.0
- Fixed in
- 1.6.0
Every github.com/gin-contrib/cors 1.3.x release
Affected: 1.3.0 to 1.3.1. Latest github.com/gin-contrib/cors: 1.7.11.
| Version | Known advisories |
|---|---|
| github.com/gin-contrib/cors 1.3.1 | CVE-2019-25211, CVE-2019-25211 |
| github.com/gin-contrib/cors 1.3.0 | CVE-2019-25211, CVE-2019-25211 |
Which of your client projects are still on github.com/gin-contrib/cors 1.3?
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.