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 13.69.68.16:443 ยท users.demo.workai.cloud
2026-01-23 06:21
HTTP/1.1 200 OK Connection: close Content-Type: text/plain; charset=utf-8 Date: Fri, 23 Jan 2026 06:22:17 GMT Set-Cookie: ARRAffinity=cd65eecb78f3b5d85f93f8c6ab30a80a8ba28d68531769e86e4d284cc7411840;Path=/;HttpOnly;Secure;Domain=users.demo.workai.cloud Set-Cookie: ARRAffinitySameSite=cd65eecb78f3b5d85f93f8c6ab30a80a8ba28d68531769e86e4d284cc7411840;Path=/;HttpOnly;SameSite=None;Secure;Domain=users.demo.workai.cloud Transfer-Encoding: chunked Strict-Transport-Security: max-age=2592000 x-trace-id: bb1a744937d898efd8a5a78b07698151 healthy