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: 5733ddf49ff49cd1aad035492586d5538062531b2c5805a7c3751c18b6a602f7
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
DELETE /v1/bucket/image/bucketurl
GET /v1/bucket/image/{imageKey}
GET /v1/bucket/image/{imageKey}/{size}
GET /v1/bucket/image/{prefix}/{imageKey}/{size}
PUT /v1/bucket/image
PUT /v1/bucket/image/raw