Cross-user data exposure via memoized render context
Published Jul 17, 2026 · Updated Jul 17, 2026
Context leakage in ViewComponent 4.0.0 through 4.11.0 allows remote authenticated users to receive stale privileged render output. ViewComponent::Base.render_in memoizes helpers, controller, request, view-flow, template details, and child context instead of resetting them for each render. Exploitation requires an application to reuse one component instance across users, tenants, or threads; ordinary per-request instantiation is unaffected.
Summary
What happened
Context leakage in ViewComponent 4.0.0 through 4.11.0 allows remote authenticated users to receive stale privileged render output. ViewComponent::Base.render_in memoizes helpers, controller, request, view-flow, template details, and child context instead of resetting them for each render. Exploitation requires an application to reuse one component instance across users, tenants, or threads; ordinary per-request instantiation is unaffected.
The record
- CVE
- CVE-2026-54497
- Published
- Jul 17, 2026
- Updated
- Jul 17, 2026
- Vendor
- ViewComponent
- Product
- ViewComponent
- Classifications
- CWE-488, CWE-668, CWE-362, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 17, 2026CVE publishedPublication date reported by the CVE source.
- Jul 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 4.0.0, < 4.12.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-9h85-g7w3-rh49 embedded proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo