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: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
Open service 20.119.128.6:443 ยท testapi.vineforce.com
2026-01-23 08:14
HTTP/1.1 302 Found Content-Length: 0 Connection: close Date: Fri, 23 Jan 2026 08:15:14 GMT Location: /swagger Set-Cookie: ARRAffinity=19afe4c451b0ae6edce365f7584cb7332ff5f0812e2374abbdf86645e2e8a2ae;Path=/;HttpOnly;Secure;Domain=testapi.vineforce.com Set-Cookie: ARRAffinitySameSite=19afe4c451b0ae6edce365f7584cb7332ff5f0812e2374abbdf86645e2e8a2ae;Path=/;HttpOnly;SameSite=None;Secure;Domain=testapi.vineforce.com