CVE-2026-54163 json
secure_headers: CSP directive injection via sandbox, plugin_types, and report_to when given untrusted input
published 4mo ago modified 18d ago also EUVD-2026-45317 , GHSA-rqq5-2gf9-4w4q
- cvss
- 4.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- rubygems secure_headers 7.3.0
- twitter secure_headers 7.3.0
Is CVE-2026-54163 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/github/secure_headers/security/advisories/GHSA-rqq5-2gf9-4w4q referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N |
| GitHub | 3.1 | 4.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | secure_headers | <7.3.0 |
7.3.0 |
Affected products
- github secure_headers
Classification
References
- github.com /github/secure_headers/commit/286a79dea80c6a9be4ca93e0f284c923cf77e539
-
github.com
/github/secure_headers/security/advisories/GHSA-rqq5-2gf9-4w4q
exploit, web
- github.com /github/secure_headers/releases/tag/v7.3.0
-
github.com
/github/secure_headers
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/secure_headers/CVE-2026-54163.yml
web
-
cve.org
/CVERecord/SearchResults?query=CVE-2026-54163
web
Sources
- CVE List CVE-2026-54163
- GitHub Advisory GHSA-rqq5-2gf9-4w4q
- NVD CVE-2026-54163
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.