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: 5733ddf49ff49cd1aad035497081a445c61c0084bcdfb6a61d5526ad58784581
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /v1/auth/aggregate/companies/{companyId}/rights
GET /v1/auth/aggregate/rights/customers
GET /v1/auth/companies/{companyId}/rights
GET /v1/auth/rights/customers
GET /v1/check/companies/{companyId}
GET /v1/check/customers/{customerId}/companies/{companyId}