Categories
CVE-2026-54498 high CVSS 8.7

Cross-Site Scripting (XSS) in view_component (CVE-2026-54498)

Summary

Cross-site scripting in view_component (CVE-2026-54498). Confidential information can be exposed externally. Exploitable via around_render. 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#around_render can return HTML-unsafe strings that bypass the escaping behavior applied to normal #call return values. This creates an XSS risk when downstream applications use around_render to wrap, replace, instrument, or conditionally return content that includes user-controlled data, and ViewComponent::Collection#render_in can amplify the issue by joining per-item results and marking the entire output html_safe, converting raw unsafe output into an ActiveSupport::SafeBuffer. 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-54498 has been found in view_component.
Attackers can target a specific entry point like around_render over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/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-54498" on the vendor's site.

CVE-2026-54498 (view_component) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Attack surface: around_render / html_safe / eea79445 / render_in
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.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in view_component. Attackers reach the vulnerable code path via around_render.

📍 Affected scope

Check the vendor advisory for the affected versions of view_component. Attack surface: around_render / html_safe / eea79445 / render_in.

🔥 Severity

Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 4.12.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify
    grep -r 'view_component' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で view_component を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade view_component to 4.12.0

    ステージング環境で 4.12.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

rubygems view_component
[{"type":"ECOSYSTEM","events":[{"introduced":"4.0.0"},{"fixed":"4.12.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details