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 23.50.131.141:443 ยท competitions-uat.fifa.org
2026-01-22 20:48
HTTP/1.1 404 Not Found Content-Type: text/html Content-Length: 179 Expires: Thu, 22 Jan 2026 20:48:21 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Thu, 22 Jan 2026 20:48:21 GMT Connection: close Akamai-GRN: 0.13173317.1769114901.25de7693 Page title: 404 Not Found <html> <head><title>404 Not Found</title></head> <body> <center><h1>404 Not Found</h1></center> <hr><center>Microsoft-Azure-Application-Gateway/v2</center> </body> </html>