Is secure_headers 6.3 vulnerable?

RubyGems · 5 releases from 6.3.0 to 6.3.4 · latest secure_headers is 7.3.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. secure_headers 6.3.4, the last 6.3 release, is affected by 1 known security advisory (1 medium), including CVE-2026-54163. Upgrade to 7.3.0 or later to fix all of them.

Upgrade with:bundle update --conservative secure_headers # Gemfile: '>= 7.3.0'

Is your project on an affected secure_headers?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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 6.3.4

  • MediumCVE-2026-54163GHSA-rqq5-2gf9-4w4q10 Jul 2026

    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

Every secure_headers 6.3.x release

Affected: 6.3.0 to 6.3.4. Latest secure_headers: 7.3.0.

VersionKnown advisories
secure_headers 6.3.4CVE-2026-54163
secure_headers 6.3.3CVE-2026-54163
secure_headers 6.3.2CVE-2026-54163
secure_headers 6.3.1CVE-2026-54163
secure_headers 6.3.0CVE-2026-54163

Which of your client projects are still on secure_headers 6.3?

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.