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: 5733ddf49ff49cd1b885ff435a26a4c644a417c2a12ceeda4176bdfad4e9815d
Public Swagger UI/API detected at path: /swagger.json - sample paths:
GET /plg_auth_check/
GET /v1/auth_check
GET /v1/change-request-logs/
GET /v1/change-request-logs/{id}/
GET /v1/change-requests/
GET /v1/change-requests/{id}/
GET /v1/data_files/
GET /v1/data_files/years
GET /v1/data_files/years/{stt}
GET /v1/data_files/{id}/
GET /v1/data_files/{id}/download/
GET /v1/data_files/{id}/download_error_report/
GET /v1/feedback/
GET /v1/feedback/{id}/
GET /v1/login/
GET /v1/logout
GET /v1/oidc/ams
GET /v1/reports/
GET /v1/reports/report-sources/
GET /v1/reports/report-sources/{id}/
GET /v1/reports/{id}/
GET /v1/reports/{id}/download/
GET /v1/roles/
GET /v1/security/get-token
GET /v1/stts/
GET /v1/stts/alpha
GET /v1/stts/by_region
GET /v1/users/
GET /v1/users/profile/
GET /v1/users/request_access/
GET /v1/users/{id}/
PATCH /v1/users/update_profile/
POST /v1/logs/
POST /v1/security/event-token
Severity: info
Fingerprint: 5733ddf49ff49cd1b885ff435a26a4c644a417c2462c12f012246220c812a5d5
Public Swagger UI/API detected at path: /swagger.json - sample paths:
GET /plg_auth_check/
GET /v1/auth_check
GET /v1/data_files/
GET /v1/data_files/years
GET /v1/data_files/years/{stt}
GET /v1/data_files/{id}/
GET /v1/data_files/{id}/download/
GET /v1/data_files/{id}/download_error_report/
GET /v1/feedback/
GET /v1/feedback/{id}/
GET /v1/login/
GET /v1/logout
GET /v1/oidc/ams
GET /v1/roles/
GET /v1/security/get-token
GET /v1/stts/
GET /v1/stts/alpha
GET /v1/stts/by_region
GET /v1/users/
GET /v1/users/request_access/
GET /v1/users/{id}/
POST /v1/logs/
Open service 56.137.118.217:443 ยท tanfdata.acf.hhs.gov
2026-01-22 22:33
HTTP/1.1 403 Forbidden
Date: Thu, 22 Jan 2026 22:33:07 GMT
Content-Type: application/json
Content-Length: 136
Connection: close
x-amzn-requestid: 2d8c24a9-5e1c-4d8a-a0b5-edc583174c9c
access-control-allow-origin: *
{"Message":"User: anonymous is not authorized to perform: es:ESHttpGet because no resource-based policy allows the es:ESHttpGet action"}