Vulnerability in view_component (CVE-2026-54497)
Summary
Vulnerability in view_component (CVE-2026-54497). Confidential information can be exposed externally. Exploitable via Host header. Mitigation: upgrade to 4.12.0 or later.
Original description
The description as published by the source.
view_component is a framework for building reusable, testable, and encapsulated view components in Ruby on Rails. From 4.0.0 until 4.12.0, ViewComponent::Base instances retain render-scoped objects across calls to render_in; if the same component, collection, or spacer component instance is reused across requests, users, tenants, or threads, later renders can use stale helpers, controller, request, view_flow, format/variant details, and slot child context from an earlier render. This can cause authorization-aware components to render privileged UI for a lower-privileged user, generate links using a stale Host header, leak slot/helper state, and mix request context under concurrent rendering. This issue is fixed in version 4.12.0.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54497 has been found in view_component.
Attackers can target a specific entry point like Host header over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade view_component to 4.12.0 or later.
If unsure, ask your IT team or search "view_component CVE-2026-54497" on the vendor's site.
CVE-2026-54497 (view_component) — CWE-362 / CVSS v3 6.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Host header / render_in / helpers / controller
Patched: 4.12.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-362) exists in view_component. Attackers reach the vulnerable code path via Host header.
Check the vendor advisory for the affected versions of view_component. Attack surface: Host header / render_in / helpers / controller.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to 4.12.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'view_component' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'view_component' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
view_componentを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade view_component to 4.12.0ステージング環境で 4.12.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com
- web github.com
- web cve.org
- web github.com