How to fix: Go Panic / Goroutine Trace Exposed
A Go panic message with a goroutine stack trace ('goroutine N [running]' plus .go file references) was found in the response body.
Why it matters
The trace discloses internal package/file paths and the full call stack leading to the crash, which helps an attacker understand the application's internal structure.
Go's default behavior on an unrecovered panic in an HTTP handler is to crash the goroutine and, depending on the server setup, can leak the panic output into the response or logs mixed with the response stream.
How to fix it
- 1Add a recover() call in HTTP middleware wrapping every handler so a panic becomes a generic 500 response.
- 2Log the full panic and stack trace server-side only.
- 3Fix the underlying nil pointer / index-out-of-range / type-assertion condition causing the panic.
Code examples
Recover middleware
func RecoverMiddleware(next http.Handler) http.Handler {
return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
defer func() {
if err := recover(); err != nil {
log.Printf("panic: %v", err)
http.Error(w, "Internal Server Error", http.StatusInternalServerError)
}
}()
next.ServeHTTP(w, r)
})
}References
Detected automatically by VulnRadar. The check id is golang-panic-trace-exposed, stable across every scan so you can filter or diff on it.
More info disclosure checks
- MediumRails Session Cookie Missing HttpOnly Flag
- InfoServer header truncated
- InfoPHP session cookie naming exposes runtime
- Infoconfig.js / settings.js referenced (verify contents)
- Infoenv.js / environment.js referenced (verify contents)
- InfoSitemap.xml publicly accessible
- InfoOpenAPI schema version exposed in URL
- LowCORS exposes internal CDN hostname
Questions
- How severe is Go Panic / Goroutine Trace Exposed?
- VulnRadar rates this medium severity in the info disclosure category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id golang-panic-trace-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Go Panic / Goroutine Trace Exposed map to?
- It maps to CWE-209. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.