Back to CVE records
Medium 6.8Published Jul 17, 2026

CVE-2026-54497view_component is a framework for building reusable, testable, and encapsulated view components in Ruby on Rails.

Updated under an hour ago ()

Does this affect you?

It affects viewcomponent view_component. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
6.8 MEDIUM (v3.1, NVD)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Weakness (CWE)
CWE-362, CWE-488, CWE-668
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Not given
NVD analysis
Analyzed
Record last updated
Jul 29, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
viewcomponent view_component
viewcomponent:view_component
from 4.0.0 before 4.12.0
NVD

References

  • patch
  • product, release-notes
  • exploit, mitigation, vendor-advisory

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.