Skip to main content
LowHeadersOWASP A05:2021CWE-200

How to fix: X-Runtime header reveals request processing time

The X-Runtime header is present, exposing per-request server processing time in milliseconds.

Why it matters

Request timing information can be used for timing-based side-channel attacks, inferring whether a user exists, whether a resource is cached, or the cost of specific operations.

Remove the X-Runtime header in production.

How to fix it

  1. 1Disable X-Runtime in your framework configuration
  2. 2Rails: config.action_dispatch.x_runtime_header = nil

Code examples

Nginx: remove runtime header

nginx
proxy_hide_header X-Runtime;

References

Detected automatically by VulnRadar. The check id is x-runtime-exposed, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is X-Runtime header reveals request processing time?
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 x-runtime-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does X-Runtime header reveals request processing time 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.

Propose a checkHow a check is built

Scan your own site for x-runtime header reveals request processing time

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

X-Runtime header reveals request processing time | VulnRadar