# CVE-2026-54497: view_component: Reused Component Instances Retain Stale Render Context

> Reusing ViewComponent instances across requests leaks stale context, potentially exposing privileged UI or data to unauthorized users.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-9h85-g7w3-rh49

## What is CVE-2026-54497?

CVE-2026-54497 is a medium-severity vulnerability in ViewComponent view_component, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere), CWE-488 (Exposure of Data Element to Wrong Session), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-54497?

2 open source packages ship an affected version, including view_component. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `view_component` | RubyGems | From 4.0.0 | 4.12.0 |
| `view_component` | RubyGems | From 4.0.0 | 4.12.0 |

Products: Viewcomponent View Component.

## How do I fix CVE-2026-54497?

Upgrade view_component to 4.12.0 or later.

## Is CVE-2026-54497 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54497 exists.

## Other vulnerabilities in ViewComponent view_component

- [CVE-2026-54498](https://insights.sbomify.com/CVE-2026-54498/): view_component: around_render HTML-Safety Bypass (high 8.7)
- [CVE-2024-21636](https://insights.sbomify.com/CVE-2024-21636/): view_component Cross-site Scripting vulnerability (medium 6.1)
- [CVE-2026-44837](https://insights.sbomify.com/CVE-2026-44837/): view_component: System Test Entry Point Path Check Allows Sibling Directory Escape (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54497 and fix it if it is affected.

What it is: CVE-2026-54497 is a medium-severity vulnerability in ViewComponent view_component, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54497 exists.

Affected packages and fixed versions:
- view_component (RubyGems): affected from 4.0.0; fixed in 4.12.0
- view_component (RubyGems): affected from 4.0.0; fixed in 4.12.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54497/ (Markdown: https://insights.sbomify.com/CVE-2026-54497/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54497
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54497
- OSV: https://osv.dev/vulnerability/CVE-2026-54497

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54497/
Summaries are generated and may contain mistakes; the official description above is the record.