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: 5733ddf49ff49cd1f5e22fb4e788b41f9351df258c45aa94d074cfa56178cb96
Public Swagger UI/API detected at path: /api/swagger.json - sample paths:
GET /jobs
GET /jobs-export
GET /jobs/{jobId}/history
GET /jobs/{jobId}/history/{historyId}
GET /jobs/{jobId}/history/{historyId}/results
GET /modules
GET /statuses
POST /RunAllJobsFunction
POST /RunSingleValidationFunction
Open service 13.69.68.12:443 · monitoring-api.czapp-dev.com
2026-01-23 14:32
HTTP/1.1 204 No Content Connection: close Date: Fri, 23 Jan 2026 14:33:20 GMT Request-Context: appId=cid-v1:db865329-f101-4bab-8b75-c39033d91b0e
Open service 13.69.68.12:80 · monitoring-api.czapp-dev.com
2026-01-12 05:38
HTTP/1.1 301 Moved Permanently Content-Length: 0 Connection: close Date: Mon, 12 Jan 2026 05:39:35 GMT Location: https://monitoring-api.czapp-dev.com/
Open service 13.69.68.12:443 · monitoring-api.czapp-dev.com
2026-01-12 05:38
HTTP/1.1 204 No Content Connection: close Date: Mon, 12 Jan 2026 05:39:35 GMT Request-Context: appId=cid-v1:db865329-f101-4bab-8b75-c39033d91b0e