Is CVE-2026-54498 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-54498 being exploited in the wild.

How severe is CVE-2026-54498?

High severity, with a CVSS score of 8.7, published 17 July 2026.

Which products and versions are affected?

GitHub ViewComponent >= 4.0.0, = 4.0.0, < 4.12.0, ECOSYSTEM:introduced=4.0.0,fixed=4.12.0.

Is there a fix for CVE-2026-54498?

Yes. view_component (RubyGems): upgrade to 4.12.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-54498 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-54498?

Check whether you run GitHub ViewComponent or view_component (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-54498: ViewComponent XSS via around_render HTML-safety bypass

Q: Is there a fix for CVE-2026-54498?

Yes. view_component (RubyGems): upgrade to 4.12.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-54498 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-54498?

Check whether you run GitHub ViewComponent or view_component (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-54498 · Severity: high · CVSS 8.7 · Published 2026-07-17

ViewComponent is a framework for building user interface components in Ruby on Rails applications. A security flaw allows certain component methods to bypass standard security protections that prevent malicious scripts from being injected into web pages. If an application uses these components to display user-provided data, an attacker could execute unauthorized scripts in other users' browsers, potentially leading to account takeover or data theft.

Technologies: GitHub ViewComponent, view_component (RubyGems). Vendors: GitHub, RubyGems.

Quick answers

Is CVE-2026-54498 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-54498 being exploited in the wild.
How severe is CVE-2026-54498?: High severity, with a CVSS score of 8.7, published 17 July 2026.
Which products and versions are affected?: GitHub ViewComponent >= 4.0.0, < 4.12.0; view_component (RubyGems) >= 4.0.0, < 4.12.0, ECOSYSTEM:introduced=4.0.0,fixed=4.12.0.
Is there a fix for CVE-2026-54498?: Yes. view_component (RubyGems): upgrade to 4.12.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54498 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-54498?: Check whether you run GitHub ViewComponent or view_component (RubyGems) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

view_component (RubyGems): upgrade to 4.12.0 or later
```
bundle update view_component
```

Technical details

A cross-site scripting (XSS) vulnerability exists in ViewComponent versions 4.0.0 through 4.11.x. The root cause is that 'ViewComponent::Base#around_render' does not apply the same HTML-escaping logic as the standard '#call' method, allowing HTML-unsafe strings to be rendered raw. This risk is significantly amplified when using 'ViewComponent::Collection#render_in', which joins per-item results and explicitly marks the entire output as 'html_safe', effectively laundering unsafe strings into trusted 'ActiveSupport::SafeBuffer' objects. An attacker can exploit this by providing malicious input that is subsequently processed by a component using 'around_render' for wrapping or instrumentation. The issue is fixed in version 4.12.0 by ensuring 'around_render' output is escaped and using 'safe_join' for collections.

Affected products

ViewComponent view_component >= 4.0.0, < 4.12.0

Identifiers

CVE-2026-54498
GHSA-97jw-64cj-jc58

Timeline

2026-06-04: patched: Fixes committed and version 4.12.0 released.
2026-07-17: disclosed: Public advisory published.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.