<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 09 Oct 2026 06:19:02 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-338960</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-338960</link>
      <description>EUVD-2026-338960</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-338960</guid>
    </item>
    <item>
      <title>fkie_cve-2026-54498</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54498</link>
      <description>&lt;p&gt;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#around_render can return HTML-unsafe strings that bypass the escaping behavior applied to normal #call return values. This creates an XSS risk when downstream applications use around_render to wrap, replace, instrument, or conditionally return content that includes user-controlled data, and ViewComponent::Collection#render_in can amplify the issue by joining per-item results and marking the entire output html_safe, converting raw unsafe output into an ActiveSupport::SafeBuffer. This issue is fixed in version 4.12.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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#around_render can return HTML-unsafe strings that bypass the escaping behavior applied to normal #call return values. This creates an XSS risk when downstream applications use around_render to wrap, replace, instrument, or conditionally return content that includes user-controlled data, and ViewComponent::Collection#render_in can amplify the issue by joining per-item results and marking the entire output html_safe, converting raw unsafe output into an ActiveSupport::SafeBuffer. This issue is fixed in version 4.12.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-54498</guid>
    </item>
    <item>
      <title>GHSA-97jw-64cj-jc58 — ViewComponent: around_render HTML-Safety Bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-97jw-64cj-jc58</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: view_component&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`ViewComponent::Base#around_render` can return HTML-unsafe strings that bypass the escaping behavior applied to normal `#call` return values. This creates an XSS risk when downstream applications use `around_render` to wrap, replace, instrument, or conditionally return content that includes user-controlled data.&lt;/p&gt;
&lt;p&gt;The issue is especially dangerous in collection rendering because `ViewComponent::Collection#render_in` joins the per-item results and marks the entire output as `html_safe`, converting raw unsafe output into a trusted `ActiveSupport::SafeBuffer`.&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;Validated against:&lt;/p&gt;
&lt;p&gt;- Repository commit: `eea79445`
- Ruby: `3.4.9`&lt;/p&gt;
&lt;p&gt;Relevant locations:&lt;/p&gt;
&lt;p&gt;- `lib/view_component/base.rb`
  - `render_in`
  - `around_render`
  - `__vc_maybe_escape_html`
- `lib/view_component/template.rb`
  - `InlineCall#safe_method_name_call`
- `lib/view_component/collection.rb`
  - `Collection#render_in`&lt;/p&gt;
&lt;p&gt;Key code paths:&lt;/p&gt;
&lt;p&gt;```ruby
# lib/view_component/base.rb
around_render do
  render_template_for(@__vc_requested_details).to_s
end
```&lt;/p&gt;
&lt;p&gt;```ruby
# lib/view_component/template.rb
proc do
  __vc_maybe_escape_html(send(m)) do
    Kernel.warn(...)
  end
end
```&lt;/p&gt;
&lt;p&gt;```ruby
# lib/view_component/collection.rb
components.map do |component|
  component.render_in(view_context, &amp;amp;block)
end.join(rendered_spacer(view_context)).html_safe
```&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;Normal inline `#call` output is passed through `__vc_maybe_escape_html`, which escapes HTML-unsafe strings. However, when `around_render`…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: view_component&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`ViewComponent::Base#around_render` can return HTML-unsafe strings that bypass the escaping behavior applied to normal `#call` return values. This creates an XSS risk when downstream applications use `around_render` to wrap, replace, instrument, or conditionally return content that includes user-controlled data.&lt;/p&gt;
&lt;p&gt;The issue is especially dangerous in collection rendering because `ViewComponent::Collection#render_in` joins the per-item results and marks the entire output as `html_safe`, converting raw unsafe output into a trusted `ActiveSupport::SafeBuffer`.&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;Validated against:&lt;/p&gt;
&lt;p&gt;- Repository commit: `eea79445`
- Ruby: `3.4.9`&lt;/p&gt;
&lt;p&gt;Relevant locations:&lt;/p&gt;
&lt;p&gt;- `lib/view_component/base.rb`
  - `render_in`
  - `around_render`
  - `__vc_maybe_escape_html`
- `lib/view_component/template.rb`
  - `InlineCall#safe_method_name_call`
- `lib/view_component/collection.rb`
  - `Collection#render_in`&lt;/p&gt;
&lt;p&gt;Key code paths:&lt;/p&gt;
&lt;p&gt;```ruby
# lib/view_component/base.rb
around_render do
  render_template_for(@__vc_requested_details).to_s
end
```&lt;/p&gt;
&lt;p&gt;```ruby
# lib/view_component/template.rb
proc do
  __vc_maybe_escape_html(send(m)) do
    Kernel.warn(...)
  end
end
```&lt;/p&gt;
&lt;p&gt;```ruby
# lib/view_component/collection.rb
components.map do |component|
  component.render_in(view_context, &amp;amp;block)
end.join(rendered_spacer(view_context)).html_safe
```&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;Normal inline `#call` output is passed through `__vc_maybe_escape_html`, which escapes HTML-unsafe strings. However, when `around_render`…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-97jw-64cj-jc58</guid>
    </item>
  </channel>
</rss>
