Is github.com/swaggo/http-swagger 1.0 vulnerable?
Go · 1 release from 1.0.0 to 1.0.0 · latest github.com/swaggo/http-swagger is 1.3.4 · checked 18 Nov 2026
Yes: 3 known advisories
Yes. github.com/swaggo/http-swagger 1.0.0, the last 1.0 release, is affected by 3 known security advisories (1 high, 1 medium, 1 low), including CVE-2022-24863, CVE-2022-24863, CVE-2022-24863. Upgrade to 1.2.6 or later to fix all of them.
go get github.com/swaggo/http-swagger@v1.2.6Is your project on an affected github.com/swaggo/http-swagger?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/swaggo/http-swagger 1.0.0
Unprotected file upload in github.com/swaggo/http-swagger
- Affected
- <1.2.6
- Fixed in
- 1.2.6
http-swagger XSS via PUT requests
- Affected
- <1.2.6
- Fixed in
- 1.2.6
Denial of Service in http-swagger
- Affected
- <1.2.6
- Fixed in
- 1.2.6
Which of your client projects are still on github.com/swaggo/http-swagger 1.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/swaggo/http-swagger version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/swaggo/http-swagger 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.