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 2.23.7.32:443 ยท plcrmgatewaytest.sentry.com
2026-01-22 18:47
HTTP/1.1 404 Not Found Content-Length: 0 Strict-Transport-Security: max-age=2592000 Expires: Thu, 22 Jan 2026 18:47:50 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Thu, 22 Jan 2026 18:47:50 GMT Connection: close Server-Timing: cdn-cache; desc=MISS Server-Timing: edge; dur=103 Server-Timing: origin; dur=24 Server-Timing: ak_p; desc="1769107670003_35063580_465249176_12652_11815_0_5_-";dur=1