<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Artur Rios Lab</title><link>https://artur-rios.github.io/personal-lab/security/</link><description>Recent content in Security on Artur Rios Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 20 Oct 2026 23:30:00 +0000</lastBuildDate><atom:link href="https://artur-rios.github.io/personal-lab/security/index.xml" rel="self" type="application/rss+xml"/><item><title>What Are CVE and CWE? Naming Vulnerabilities and the Weaknesses Behind Them</title><link>https://artur-rios.github.io/personal-lab/security/cve-and-cwe/</link><pubDate>Tue, 20 Oct 2026 23:30:00 +0000</pubDate><guid>https://artur-rios.github.io/personal-lab/security/cve-and-cwe/</guid><description>&lt;p&gt;A dependency scanner fails your build with &amp;ldquo;CVE-2021-44228, critical&amp;rdquo;. A static&#10;analysis tool flags a line of code as &amp;ldquo;CWE-89&amp;rdquo;. A vendor&amp;rsquo;s release notes list&#10;a dozen CVE numbers fixed in the latest patch, and a security questionnaire&#10;asks how you prevent &amp;ldquo;the CWE Top 25&amp;rdquo;. The two acronyms look alike, both are&#10;run by the same organisation and both turn up in the same tools, but they&#10;answer different questions. &lt;strong&gt;CVE&lt;/strong&gt; answers &lt;em&gt;which vulnerability is this?&lt;/em&gt;: it&#10;gives one specific, publicly known flaw in one product a name everyone can&#10;use. &lt;strong&gt;CWE&lt;/strong&gt; answers &lt;em&gt;what kind of mistake is this?&lt;/em&gt;: it names a type of&#10;weakness that can occur in any product, and that may cause many&#10;vulnerabilities over the years.&lt;/p&gt;</description></item></channel></rss>