Is secure_headers 5.1 vulnerable?
RubyGems · 1 release from 5.1.0 to 5.1.0 · latest secure_headers is 7.3.0 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. secure_headers 5.1.0, the last 5.1 release, is affected by 2 known security advisories (2 medium), including CVE-2026-54163, CVE-2020-5216. Upgrade to 7.3.0 or later to fix all of them.
bundle update --conservative secure_headers # Gemfile: '>= 7.3.0'Is your project on an affected secure_headers?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting secure_headers 5.1.0
Secure Headers: CSP directive injection via sandbox, plugin_types, and report_to when given untrusted input
- Affected
- <7.3.0
- Fixed in
- 7.3.0
Limited header injection when using dynamic overrides with user input in RubyGems secure_headers
- Affected
- >=6.0.0 <6.3.0 · >=5.0.0 <5.2.0 · <3.9.0
- Fixed in
- 3.9.0, 5.2.0, 6.3.0
Which of your client projects are still on secure_headers 5.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact secure_headers version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other secure_headers versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.