Cross-site Scripting (XSS) Affecting ruby-secure-headers package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-RUBYSECUREHEADERS-18016429
- published19 Jul 2026
- disclosed17 Jul 2026
Introduced: 17 Jul 2026
CVE-2026-54163 (opens in a new tab)How to fix?
There is no fixed version for Echo:latest ruby-secure-headers.
NVD Description
Note: Versions mentioned in the description apply only to the upstream ruby-secure-headers package and not the ruby-secure-headers package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
secure_headers manages application of security headers with many safe defaults. Prior to 7.3.0, secure_headers builds the Content-Security-Policy value by stitching directives with ; separators, and build_sandbox_list_directive, build_media_type_list_directive, and build_report_to_directive interpolate caller-supplied strings without scrubbing ;, \r, or \n. When untrusted input reaches SecureHeaders.override_content_security_policy_directives or append APIs for :sandbox, :plugin_types, or :report_to, an attacker can inject a CSP directive such as script-src 'unsafe-inline' * before the legitimate script-src, enabling XSS reachability through these sinks or CSP report exfiltration. This issue is fixed in version 7.3.0.