Is github.com/swaggo/http-swagger 1.2 vulnerable?
Go · 6 releases from 1.2.0 to 1.2.8 · latest github.com/swaggo/http-swagger is 1.3.4 · checked 18 Nov 2026
No known advisories in the last release
github.com/swaggo/http-swagger 1.2.8, the last 1.2 release, has no known advisories. 3 advisories affect earlier 1.2.x releases, so update to 1.2.8.
go get github.com/swaggo/http-swagger@v1.2.8Is 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
Fixed within 1.2.x, affecting earlier releases
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
Every github.com/swaggo/http-swagger 1.2.x release
Affected: 1.2.0 to 1.2.5. 1.2.6 and later are not affected. Latest github.com/swaggo/http-swagger: 1.3.4.
| Version | Known advisories |
|---|---|
| github.com/swaggo/http-swagger 1.2.8 | None |
| github.com/swaggo/http-swagger 1.2.7 | None |
| github.com/swaggo/http-swagger 1.2.6 | None |
| github.com/swaggo/http-swagger 1.2.5 | CVE-2022-24863, CVE-2022-24863, CVE-2022-24863 |
| github.com/swaggo/http-swagger 1.2.1 | CVE-2022-24863, CVE-2022-24863, CVE-2022-24863 |
| github.com/swaggo/http-swagger 1.2.0 | CVE-2022-24863, CVE-2022-24863, CVE-2022-24863 |
Which of your client projects are still on github.com/swaggo/http-swagger 1.2?
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.