<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CVSS (Common Vulnerability Scoring System) on Rietta Cybersecurity</title>
    <link>https://rietta.com/glossary/cvss/</link>
    <description>Recent content in CVSS (Common Vulnerability Scoring System) on Rietta Cybersecurity</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>1999-2026 Rietta Inc. All Rights Reserved.</copyright>
    <lastBuildDate>Tue, 20 Oct 2026 10:13:26 -0400</lastBuildDate>
    <atom:link href="https://rietta.com/glossary/cvss/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Government Rails Site Hit Hours After CVE Patch</title>
      <link>https://rietta.com/blog/ruby-on-rails-cve-exploited-hours-after-patch/</link>
      <pubDate>Fri, 04 Sep 2026 12:55:00 -0400</pubDate>
      <guid>https://rietta.com/blog/ruby-on-rails-cve-exploited-hours-after-patch/</guid>
      <description>After hours on Wednesday, July 29, 2026, Rietta executed our emergency hotfix procedure across our entire client base for sites impacted by a severe remote code execution vulnerability in ActiveStorage, a component of Ruby on Rails 8 and newer. We worked off the initial GitHub Security Advisory, published the same day the patch shipped. Ethiack, one of the research teams that discovered the flaw, dubbed it KindaRails2Shell (CVE-2026-66066) in their initial disclosure post that same day, July 29th, with a full technical deep-dive following the next day on July 30th.</description>
    </item>
    <item>
      <title>Threat Modeling for ADA/WCAG Compliance</title>
      <link>https://rietta.com/blog/threat-modeling-ada-wcag-compliance/</link>
      <pubDate>Tue, 28 Jul 2026 14:00:00 +0000</pubDate>
      <guid>https://rietta.com/blog/threat-modeling-ada-wcag-compliance/</guid>
      <description>Why Accessibility Belongs in Your Threat Model Most organizations treat digital accessibility as a content problem: someone finds a missing alt tag, fixes it, and moves on. I think that&amp;rsquo;s the wrong frame entirely. Digital accessibility is an organizational risk and governance gap, and once you see it that way, the right tool for the job isn&amp;rsquo;t a content checklist. It&amp;rsquo;s the same discipline we already use for application security: threat modeling and continuous technical monitoring.</description>
    </item>
    <item>
      <title>Ruby Gems Supply Chain Vulnerability</title>
      <link>https://rietta.com/blog/rubygems-supply-chain-vulnerability/</link>
      <pubDate>Fri, 06 Sep 2019 11:00:00 -0400</pubDate>
      <guid>https://rietta.com/blog/rubygems-supply-chain-vulnerability/</guid>
      <description>&lt;p&gt;Every Ruby on Rails application depends on Ruby Gems, the third party open source libraries that make development possible. A brand new Ruby on Rails 6 application, with default options, depends upon 75 Gems before the developer makes any customizations to the app! These Gems are produced by volunteer open source maintainers, many of whom are not paid anything to work on open source, and distributed for free via &lt;a href=&#34;https://rubygems.org/&#34;&gt;rubygems.org&lt;/a&gt;. This is a fantastic resource that makes it possible to create so many good Ruby-based applications with minimum effort re-inventing the wheel. However, how is a developer to know the Gems he or she has in a project are in fact safe.&lt;/p&gt;&#xA;&lt;p&gt;There have been malicious backdoors distributed in multiple Gems this year. These supply chain attacks have been detected and remediated by the RubyGems community, but it will happen again. Let&amp;rsquo;s look at the patterns common among the malicious Gems and the how you can go about protecting your own application.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
