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: 5733ddf49ff49cd1aad035498685cb0f75a682a70e2681d49f72b12db729802c
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/Payer/Payers
GET /api/v1/RevenueCollection/Billers
GET /api/v1/RevenueCollection/Billers/{billerId}/Products
GET /api/v1/RevenueCollection/Collections/ByRef/{ref}
GET /api/v1/RevenueCollection/Collections/{revenueCollectionId}
POST /api/v1/RevenueCollection/CreateCollection
Open service 142.250.186.147:443 · api.payunimaid.net
2026-01-22 22:31
HTTP/1.1 404 Not Found x-cloud-trace-context: fd95b67a4f3e0ca066509adb29e02302 date: Thu, 22 Jan 2026 22:31:20 GMT content-type: text/html server: Google Frontend Content-Length: 0 Connection: close
Open service 142.250.186.147:443 · api.payunimaid.net
2026-01-10 02:29
HTTP/1.1 404 Not Found x-cloud-trace-context: df70080947cf9603523c4adff8ae4022 date: Sat, 10 Jan 2026 02:29:49 GMT content-type: text/html server: Google Frontend Content-Length: 0 Connection: close