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: 5733ddf49ff49cd1aad03549eb5cdc9b17fda90aa39fd5057d65c1ef290dba33
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /WeatherForecast GET /api/AtfSite/EmailCert GET /api/AtfSite/GetATFSite GET /api/AtfSite/GetFillsByATFSite POST /api/AtfSite/sendCerts
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549eb5cdc9b17fda90aa39fd5057d65c1ef7d65c1ef
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /WeatherForecast GET /api/AtfSite/EmailCert GET /api/AtfSite/GetATFSite GET /api/AtfSite/GetFillsByATFSite
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549eb5cdc9b557211b610daef1c10daef1c10daef1c
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /WeatherForecast GET /api/AtfSite/GetATFSite GET /api/AtfSite/GetFillsByATFSite