How to fix: .env File Reference Detected
References to .env file found in page source.
Why it matters
Exposed .env files contain database credentials, API keys, and secrets.
.env files should never be web-accessible.
How to fix it
- 1Block .env access in web server config.
Code examples
Block access to .env files via web server
# Block .env and related files from being served
location ~* /\.env {
deny all;
return 404;
}
# Store .env files outside the web root
# In Next.js: .env.local is never served, but verify your web server config
# For Docker: use ARG/ENV in Dockerfile or a secrets manager, not .env filesReferences
Detected automatically by VulnRadar. The check id is env-file-reference, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is .env File Reference Detected?
- VulnRadar rates this critical severity in the content 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 env-file-reference, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does .env File Reference Detected map to?
- It maps to CWE-538. 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.