Categories
CVE-2026-44836 medium CVSS 6.5

Vulnerability in view_component (CVE-2026-44836)

Summary

Vulnerability in view_component (CVE-2026-44836). Confidential information can be exposed externally. Exploitable via GET /rails/view_components/my_component/render_with_template. Mitigation: upgrade to 4.9.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 3.0.0 to 4.9.0, the preview route derives an example name from the URL and calls it with public_send. The code does not verify that the requested method is one of the preview examples explicitly defined by the preview class. As a result, inherited public methods on ViewComponent::Preview are route-reachable. The most important one is render_with_template, which accepts template: and locals:. Those values can come from request params and are later passed to Rails as render template:. If previews are exposed, an attacker can render internal Rails templates that are not otherwise routable. This vulnerability is fixed in 4.9.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-44836 has been found in view_component.
Attackers can target a specific entry point like GET /rails/view_components/my_component/render_with_template over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade view_component to 4.9.0 or later.
If unsure, ask your IT team or search "view_component CVE-2026-44836" on the vendor's site.

CVE-2026-44836 (view_component) — CWE-749 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /rails/view_components/my_component/render_with_template / public_send / render_with_template / render_args
Patched: 4.9.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

A vulnerability (CWE-749) exists in view_component. Attackers reach the vulnerable code path via GET /rails/view_components/my_component/render_with_template.

📍 Affected scope

Check the vendor advisory for the affected versions of view_component. Attack surface: GET /rails/view_components/my_component/render_with_template / public_send / render_with_template / render_args.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 4.9.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 GET /rails/view_components/my_component/render_with_template requests with malformed payloads or SQL meta-characters. 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
    Hunt for indicators of compromise detect
    grep 'GET /rails/view_components/my_component/render_with_template' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /rails/view_components/my_component/render_with_template への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade view_component to 4.9.0

    ステージング環境で 4.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against GET /rails/view_components/my_component/render_with_template on staging to confirm patch closes the vector

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

Affected packages

rubygems view_component
[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"4.9.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

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