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
Open service 23.50.131.154:443 ยท uat-bucket-api.commercialrealestate.com.au
2026-01-22 21:58
HTTP/1.1 403 Forbidden Mime-Version: 1.0 Content-Type: text/html Content-Length: 408 Cache-Control: max-age=0 Date: Thu, 22 Jan 2026 21:58:06 GMT Connection: close Alt-Svc: h3=":443"; ma=93600 Strict-Transport-Security: max-age=86400 ; includeSubDomains Page title: Access Denied <HTML><HEAD> <TITLE>Access Denied</TITLE> </HEAD><BODY> <H1>Access Denied</H1> You don't have permission to access "http://uat-bucket-api.commercialrealestate.com.au/" on this server.<P> Reference #18.12173317.1769119086.3d4ed6c6 <P>https://errors.edgesuite.net/18.12173317.1769119086.3d4ed6c6</P> </BODY> </HTML>