How to fix: Server header reveals detailed version number
The Server header exposes the exact version of the web server software, enabling targeted version-specific attacks.
Why it matters
An exact version like "nginx/1.18.0" allows an attacker to instantly identify applicable CVEs and patch status, removing the need to probe for vulnerabilities manually.
Set Server to a product-only token without version, or remove it entirely.
How to fix it
- 1Nginx: server_tokens off removes the version number
- 2Apache: ServerTokens Prod shows only "Apache" without version
- 3Consider removing the header entirely via middleware
Code examples
Nginx: hide version
server_tokens off; # Shows "nginx" without version
# To hide name entirely, use a custom token:
# server_tokens "x";References
Detected automatically by VulnRadar. The check id is server-version-detailed, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Server header reveals detailed version number?
- VulnRadar rates this low severity in the headers 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 server-version-detailed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Server header reveals detailed version number map to?
- It maps to CWE-200. 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.