<?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>Mon, 16 Nov 2026 21:13:44 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-404641</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-404641</link>
      <description>EUVD-2026-404641</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-404641</guid>
    </item>
    <item>
      <title>fkie_cve-2026-126084</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-126084</link>
      <description>&lt;p&gt;Active Storage makes it simple to upload and reference files in cloud services and attach those files to Active Record objects. Prior to 8.1.4.1 and 8.0.5.2, when a GCS service is configured with the cache_control option, ActiveStorage::Service::GCSService#url_for_direct_upload signs direct-upload URLs with V4, and the V4 signature covers only the Cache-Control and Host headers. A direct-upload client can therefore send a Content-Type of its choosing, and can omit the declared Content-MD5, without invalidating the URL. GCS stores the supplied content type as object metadata, which takes precedence over the response-content-type that Active Storage sets on download URLs, so an uploaded object could be served as inline HTML under the application&amp;#39;s bucket path on storage.googleapis.com. Script in such an object runs on the storage origin rather than the application&amp;#39;s, but could register a Service Worker scoped to the bucket path and read or replace a victim&amp;#39;s later responses for signed URLs in that bucket. Applications that use the GCS service with cache_control configured and accept direct uploads are affected. GCS services without cache_control sign with V2 and are not affected. This issue is fixed in versions 8.1.4.1 and 8.0.5.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Active Storage makes it simple to upload and reference files in cloud services and attach those files to Active Record objects. Prior to 8.1.4.1 and 8.0.5.2, when a GCS service is configured with the cache_control option, ActiveStorage::Service::GCSService#url_for_direct_upload signs direct-upload URLs with V4, and the V4 signature covers only the Cache-Control and Host headers. A direct-upload client can therefore send a Content-Type of its choosing, and can omit the declared Content-MD5, without invalidating the URL. GCS stores the supplied content type as object metadata, which takes precedence over the response-content-type that Active Storage sets on download URLs, so an uploaded object could be served as inline HTML under the application&amp;#39;s bucket path on storage.googleapis.com. Script in such an object runs on the storage origin rather than the application&amp;#39;s, but could register a Service Worker scoped to the bucket path and read or replace a victim&amp;#39;s later responses for signed URLs in that bucket. Applications that use the GCS service with cache_control configured and accept direct uploads are affected. GCS services without cache_control sign with V2 and are not affected. This issue is fixed in versions 8.1.4.1 and 8.0.5.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-126084</guid>
    </item>
    <item>
      <title>GHSA-3w93-6hmw-whh4 — Active Storage: Unsigned Content-Type in GCS direct uploads with cache_control</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3w93-6hmw-whh4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: activestorage&lt;/p&gt;
&lt;p&gt;### Impact
When a GCS service is configured with the `cache_control` option, `ActiveStorage::Service::GCSService#url_for_direct_upload` signs direct-upload URLs with V4, and the V4 signature covers only the `Cache-Control` and `Host` headers. A direct-upload client can therefore send a `Content-Type` of its choosing, and can omit the declared `Content-MD5`, without invalidating the URL. GCS stores the supplied content type as object metadata, which takes precedence over the `response-content-type` that Active Storage sets on download URLs, so an uploaded object could be served as inline HTML under the application&amp;#39;s bucket path on `storage.googleapis.com`. Script in such an object runs on the storage origin rather than the application&amp;#39;s, but could register a Service Worker scoped to the bucket path and read or replace a victim&amp;#39;s later responses for signed URLs in that bucket.&lt;/p&gt;
&lt;p&gt;Applications that use the GCS service with `cache_control` configured and accept direct uploads are affected. GCS services without `cache_control` sign with V2 and are not affected.&lt;/p&gt;
&lt;p&gt;### Details
The fixed releases sign every GCS direct-upload URL with V2, which binds an empty `Content-Type` and the declared `Content-MD5`. The configured `Cache-Control` is still returned by `headers_for_direct_upload` and sent by the client, but it is no longer part of the signature, and direct-upload URLs for these services are no longer limited to V4&amp;#39;s seven-day maximum expiry. See the Active Storage CHANGELOG.&lt;/p&gt;
&lt;p&gt;### Wo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: activestorage&lt;/p&gt;
&lt;p&gt;### Impact
When a GCS service is configured with the `cache_control` option, `ActiveStorage::Service::GCSService#url_for_direct_upload` signs direct-upload URLs with V4, and the V4 signature covers only the `Cache-Control` and `Host` headers. A direct-upload client can therefore send a `Content-Type` of its choosing, and can omit the declared `Content-MD5`, without invalidating the URL. GCS stores the supplied content type as object metadata, which takes precedence over the `response-content-type` that Active Storage sets on download URLs, so an uploaded object could be served as inline HTML under the application&amp;#39;s bucket path on `storage.googleapis.com`. Script in such an object runs on the storage origin rather than the application&amp;#39;s, but could register a Service Worker scoped to the bucket path and read or replace a victim&amp;#39;s later responses for signed URLs in that bucket.&lt;/p&gt;
&lt;p&gt;Applications that use the GCS service with `cache_control` configured and accept direct uploads are affected. GCS services without `cache_control` sign with V2 and are not affected.&lt;/p&gt;
&lt;p&gt;### Details
The fixed releases sign every GCS direct-upload URL with V2, which binds an empty `Content-Type` and the declared `Content-MD5`. The configured `Cache-Control` is still returned by `headers_for_direct_upload` and sent by the client, but it is no longer part of the signature, and direct-upload URLs for these services are no longer limited to V4&amp;#39;s seven-day maximum expiry. See the Active Storage CHANGELOG.&lt;/p&gt;
&lt;p&gt;### Wo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3w93-6hmw-whh4</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-126084</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-126084</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: rails, Ubuntu:Pro:18.04:LTS: rails, Ubuntu:Pro:20.04:LTS: rails, Ubuntu:Pro:22.04:LTS: rails, Ubuntu:24.04:LTS: rails, Ubuntu:26.10: rails, Ubuntu:26.04:LTS: rails&lt;/p&gt;
&lt;p&gt;Active Storage makes it simple to upload and reference files in cloud services and attach those files to Active Record objects. Prior to 8.1.4.1 and 8.0.5.2, when a GCS service is configured with the cache_control option, ActiveStorage::Service::GCSService#url_for_direct_upload signs direct-upload URLs with V4, and the V4 signature covers only the Cache-Control and Host headers. A direct-upload client can therefore send a Content-Type of its choosing, and can omit the declared Content-MD5, without invalidating the URL. GCS stores the supplied content type as object metadata, which takes precedence over the response-content-type that Active Storage sets on download URLs, so an uploaded object could be served as inline HTML under the application&amp;#39;s bucket path on storage.googleapis.com. Script in such an object runs on the storage origin rather than the application&amp;#39;s, but could register a Service Worker scoped to the bucket path and read or replace a victim&amp;#39;s later responses for signed URLs in that bucket. Applications that use the GCS service with cache_control configured and accept direct uploads are affected. GCS services without cache_control sign with V2 and are not affected. This issue is fixed in versions 8.1.4.1 and 8.0.5.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: rails, Ubuntu:Pro:18.04:LTS: rails, Ubuntu:Pro:20.04:LTS: rails, Ubuntu:Pro:22.04:LTS: rails, Ubuntu:24.04:LTS: rails, Ubuntu:26.10: rails, Ubuntu:26.04:LTS: rails&lt;/p&gt;
&lt;p&gt;Active Storage makes it simple to upload and reference files in cloud services and attach those files to Active Record objects. Prior to 8.1.4.1 and 8.0.5.2, when a GCS service is configured with the cache_control option, ActiveStorage::Service::GCSService#url_for_direct_upload signs direct-upload URLs with V4, and the V4 signature covers only the Cache-Control and Host headers. A direct-upload client can therefore send a Content-Type of its choosing, and can omit the declared Content-MD5, without invalidating the URL. GCS stores the supplied content type as object metadata, which takes precedence over the response-content-type that Active Storage sets on download URLs, so an uploaded object could be served as inline HTML under the application&amp;#39;s bucket path on storage.googleapis.com. Script in such an object runs on the storage origin rather than the application&amp;#39;s, but could register a Service Worker scoped to the bucket path and read or replace a victim&amp;#39;s later responses for signed URLs in that bucket. Applications that use the GCS service with cache_control configured and accept direct uploads are affected. GCS services without cache_control sign with V2 and are not affected. This issue is fixed in versions 8.1.4.1 and 8.0.5.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-126084</guid>
    </item>
  </channel>
</rss>
