Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-9h85-g7w3-rh49 | ViewComponent: Reused Component Instances Retain Stale Render Context |
Mon, 20 Jul 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 17 Jul 2026 23:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Viewcomponent
Viewcomponent view Component |
|
| Vendors & Products |
Viewcomponent
Viewcomponent view Component |
Fri, 17 Jul 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | view_component: Reused Component Instances Retain Stale Render Context | |
| Weaknesses | CWE-362 CWE-488 CWE-668 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-07-20T13:46:20.930Z
Reserved: 2026-06-15T18:01:15.511Z
Link: CVE-2026-54497
Updated: 2026-07-20T13:46:05.788Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-07-22T01:45:15Z
Github GHSA