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: 5733ddf49ff49cd1926e27d0926e27d0926e27d0926e27d0926e27d0926e27d0
Public Swagger UI/API detected at path: /webjars/swagger-ui/index.html
Open service 65.9.175.104:443 ยท alumni.uschamber.com
2026-01-08 22:09
HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8 Transfer-Encoding: chunked Connection: close Date: Thu, 08 Jan 2026 22:09:55 GMT X-Frame-Options: DENY X-Xss-Protection: 1; mode=block Cache-Control: no-store, no-cache Content-Security-Policy: object-src 'none'; script-src * data: blob: 'unsafe-inline' 'unsafe-eval'; child-src * data: blob: 'unsafe-inline'; style-src * data: blob: 'unsafe-inline'; font-src * data: blob: 'unsafe-inline'; ETag: "66jc799xp01161" Expires: 0 Permissions-Policy: geolocation=(self), camera=(), microphone=(), payment=(), usb=(), bluetooth=(), accelerometer=(), gyroscope=(), magnetometer=(), clipboard-read=(), clipboard-write=(), encrypted-media=(), notifications=(), push=(), sync-xhr=(), vibrate=(); Pragma: no-cache Referrer-Policy: strict-origin-when-cross-origin Strict-Transport-Security: max-age=31536000; includeSubDomains X-Content-Type-Options: nosniff Vary: Accept-Encoding X-Cache: Miss from cloudfront Via: 1.1 7aa3bfb1af156515af943236e80f9b56.cloudfront.net (CloudFront) X-Amz-Cf-Pop: FRA60-P14 X-Amz-Cf-Id: _n9MYLGTOcYh__0S-NuxzgobzJ0mo0T-mBINQqB2nREBp9tTVE_Cow==