What Is Exposed OpenAPI / Swagger?
Frameworks like FastAPI, NestJS, and many Node setups auto-generate an OpenAPI (Swagger) spec and interactive docs. Left exposed in production at /docs, /redoc, /swagger, or /openapi.json, they publish your entire API surface — every endpoint, parameter, auth scheme, and data model. That is invaluable for development and equally invaluable to an attacker planning which endpoints to probe. We scan for exposed specs and the endpoints they reveal.
How Exposed OpenAPI / Swagger Shows Up
Public interactive docs
/docs, /redoc, and /swagger expose a clickable map of every endpoint and its parameters.
Raw spec files
/openapi.json and /swagger.json hand attackers a machine-readable inventory of your API to automate testing.
Leaked internal endpoints
Specs often include admin, internal, or debug routes that were never meant to be discoverable.
Schema-driven attacks
Exposed schemas reveal field names that enable mass-assignment and parameter-tampering attacks.
How the Sable Scan Detects It
Spec discovery
We probe common doc and spec paths to find exposed OpenAPI/Swagger endpoints.
Surface mapping
When a spec is exposed, we enumerate the endpoints it reveals and test the high-risk ones for auth and IDOR.
Remediation
You get guidance to disable or authenticate docs in production (e.g. docs_url=None or gating behind auth).
Check Your App for Exposed OpenAPI / Swagger
Create a free account and let the agents test your app. Every finding is validated with a proof-of-concept and remediation. 150 founder credits, no credit card.
Get 150 Free Credits