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.
CVE-2026-54497
MEDIUMPre-NVD 6.86.8—Elevated
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.8
- EG Score
- 6.8(medium)
- EPSS
- 23.5%
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 20, 2026
Advisory Details (3)
Auto-updated Jul 17, 2026🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available
Reused Component Instances Retain Stale Render Context · Advisory · ViewComponent/view_component · GitHub
https://github.com/ViewComponent/view_component/security/advisories/GHSA-9h85-g7w3-rh49github_release Patch Available
4.12.0
Patch available: ViewComponent/view_component v4.12.0
https://github.com/ViewComponent/view_component/releases/tag/v4.12.0github_commit Patch Available
commit 6796b2e89d0b (ViewComponent/view_component)
Patch available: ViewComponent/view_component v4.12.0 (contains commit 6796b2e89d0b)
https://github.com/ViewComponent/view_component/commit/6796b2e89d0bd7b9d7d763a86275e5334731dd61Vendor Advisories for CVE-2026-54497(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
RubyGems(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| view_component | 4.0.0 ... 4.9.0 (15 versions) | 4.12.0 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:36 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-15 22:54 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-54497?
CVE-2026-54497 is a medium vulnerability published on July 15, 2026. viewcomponent 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 renderin; if the same component, collection, or spacer component instance is reused…
When was CVE-2026-54497 disclosed?
CVE-2026-54497 was first published in the National Vulnerability Database on July 15, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54497 actively exploited?
CVE-2026-54497 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54497?
CVE-2026-54497 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-54497?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54497, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54497
Is Your Infrastructure Affected by CVE-2026-54497?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.