<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CVE (Common Vulnerabilities and Exposures) on Rietta Cybersecurity</title>
    <link>https://rietta.com/glossary/cve/</link>
    <description>Recent content in CVE (Common Vulnerabilities and Exposures) 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/cve/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What is a CVE in Software Security?</title>
      <link>https://rietta.com/learning/appsec/what-is-a-cve/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://rietta.com/learning/appsec/what-is-a-cve/</guid>
      <description>A quick explainer on what a CVE (Common Vulnerabilities and Exposures) is, and why staying current on them is a non-negotiable part of running a secure application.</description>
    </item>
    <item>
      <title>How to Efficiently Patch a Ruby on Rails Application When a Critical CVE Drops</title>
      <link>https://rietta.com/learning/appsec/patching-rails-critical-cve-atlrug/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://rietta.com/learning/appsec/patching-rails-critical-cve-atlrug/</guid>
      <description>A walkthrough of efficiently patching a Ruby on Rails application when a critical CVE drops, using CVE-2022-32224 (an ActiveRecord vulnerability affecting YAML-serialized fields) as the working example. The principles apply broadly, well beyond that one CVE. Recorded at the monthly Atlanta Ruby Users&amp;rsquo; Group (ATLRUG) meeting on July 13, 2022.</description>
    </item>
    <item>
      <title>RubyGems Open Source Supply Chain Security and OpenAI</title>
      <link>https://rietta.com/blog/rubygems-supply-chain-openai/</link>
      <pubDate>Mon, 14 Sep 2026 14:00:00 +0000</pubDate>
      <guid>https://rietta.com/blog/rubygems-supply-chain-openai/</guid>
      <description>Over the weekend it has been widely reported that OpenAI agents attacked RubyGems on May 11, 2026, two months before Hugging Face, including by mainstream wire service Reuters.&#xA;The use of Artificial Intelligence frontier models both for good and for evil is happening now regardless of what any particular individual or company wishes were the case. In this case, OpenAI saying that it did not have the intent to perform the particular attack does little to show that its amoral agent (as in a computer system with no moral agency) did not pattern match and actually perform malicious activity.</description>
    </item>
    <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>The Imminent Funding Lapse of the CVE Database: A Cybersecurity Crisis</title>
      <link>https://rietta.com/blog/cve-program-funding-lapse-national-security/</link>
      <pubDate>Wed, 16 Apr 2025 12:00:00 +0000</pubDate>
      <guid>https://rietta.com/blog/cve-program-funding-lapse-national-security/</guid>
      <description>News started breaking yesterday of an imminent funding lapse for the United States government-funded Common Vulnerabilities and Exposures database maintained for the last 25 years under contract with MITRE Corporation. The reporting yesterday included Funding Expires for Key Cyber Vulnerability Database (krebsonsecurity.com) and this lapse has been confirmed by multiple sources CVE program faces swift end after DHS fails to renew contract, leaving security flaw tracking in limbo (csoonline.com) and CVE Program Funding Expires—What It Means And What To Do Next (forbes.</description>
    </item>
  </channel>
</rss>
