How to fix: Insomnia workspace export publicly served
An Insomnia workspace export is served from this URL, identified by the fields Insomnia writes. The export holds every saved request in the workspace, plus the environment values those requests interpolate.
Why it matters
The export contains every saved request in the workspace: URLs, bodies, and headers, plus the environment objects those requests interpolate. Environments are where API keys and tokens are stored, so an exported workspace frequently ships working credentials alongside the exact requests they authorize.
Same root cause as a published Postman collection, different tool. Insomnia's export format nests requests and environments in one JSON document, so a single file can disclose both the internal API surface and the secrets used to call it. Assume anything in the environment section is compromised rather than trying to judge whether a particular value looks live.
How to fix it
- 1Remove the export from the served origin, and purge it from git history if it contained secrets.
- 2Rotate every credential stored in the workspace's environments.
- 3Use Insomnia's private environments (which are excluded from exports) for secrets, and share workspaces through Insomnia Sync rather than a file.
Code examples
Find Insomnia exports in the tree
grep -rl '"__export_source"' . --include='*.json' 2>/dev/null
echo 'Insomnia_*.json' >> .gitignoreReferences
Detected automatically by VulnRadar. The check id is api-insomnia-export-exposed, stable across every scan so you can filter or diff on it.
More api checks
- LowTRACE method referenced in API response body
- InfoREST endpoint allows DELETE
- LowGraphQL introspection field suggestions
- MediumGraphQL endpoint has no rate-limit headers
- LowOpenAPI server URL leaks internal host
- LowCORS preflight result not cached
- HighBearer token in URL query string
- MediumJSONP callback parameter accepted
Questions
- How severe is Insomnia workspace export publicly served?
- VulnRadar rates this medium severity in the api category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id api-insomnia-export-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Insomnia workspace export publicly served map to?
- It maps to CWE-540. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.