Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1926e27d0926e27d0926e27d0926e27d0926e27d0926e27d0
Public Swagger UI/API detected at path: /webjars/swagger-ui/index.html
Open service 23.50.131.146:443 ยท mortgage.wellsfargo.com
2026-01-23 08:58
HTTP/1.1 404 Not Found
Content-Type: application/json
Vary: Origin
Vary: Access-Control-Request-Method
Vary: Access-Control-Request-Headers
Content-Length: 89
Date: Fri, 23 Jan 2026 08:58:35 GMT
Connection: close
Set-Cookie: 36acbcf742c97fed2d2c1f74e5e97922=57e3c3430eaefd7b2bb2558e0000568b; path=/; HttpOnly
Set-Cookie: IHTBDKLQ=028137a6b1-1290-4f__nkM6BOjB2fslNNH4CyEB2ZNIwklVzCRY9HpuYOriTK8-lEfCIDjci_u0I4iyYTMqY; path=/; SameSite=None; Secure
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
{"timestamp":"2026-01-23T08:58:35.594+00:00","status":404,"error":"Not Found","path":"/"}