<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Chad Serino</title>
    <description>The latest articles on DEV Community by Chad Serino (@chad_serino_33).</description>
    <link>https://dev.to/chad_serino_33</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4255911%2F0d87b34e-8f9f-4791-afab-952dafbf0cbd.jpg</url>
      <title>DEV Community: Chad Serino</title>
      <link>https://dev.to/chad_serino_33</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/chad_serino_33"/>
    <language>en</language>
    <item>
      <title>Your engineers are patching code they never wrote</title>
      <dc:creator>Chad Serino</dc:creator>
      <pubDate>Fri, 20 Nov 2026 14:42:24 +0000</pubDate>
      <link>https://dev.to/chad_serino_33/your-engineers-are-patching-code-they-never-wrote-45e1</link>
      <guid>https://dev.to/chad_serino_33/your-engineers-are-patching-code-they-never-wrote-45e1</guid>
      <description>&lt;p&gt;&lt;em&gt;This post first ran on the &lt;a href="https://seeghost.dev/blog/cve-noise/" rel="noopener noreferrer"&gt;Ghost blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Run a scanner on almost any container image and you get a long list. Critical. High. Medium. Pages of it.&lt;/p&gt;

&lt;p&gt;Now look at where those findings live. Most of them aren't in your code. They're in the operating system packages and runtime under it. Your team didn't write that code. But your team gets the ticket.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;&lt;a href="https://seeghost.dev/blog/cve-noise/" rel="noopener noreferrer"&gt;Interactive graphic on the original post: a raw scan queue next to a Ghost queue.&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The list only gets longer
&lt;/h2&gt;

&lt;p&gt;2025 set a record, with &lt;a href="https://mondoo.com/vulnerability-intelligence/state-of-vulnerabilities-2026" rel="noopener noreferrer"&gt;48,175 CVEs published&lt;/a&gt;. 2026 left that pace behind. Google's threat intelligence team found that &lt;a href="https://cloud.google.com/blog/topics/threat-intelligence/vulnerability-discovery-and-exploitation-trends-in-the-ai-era" rel="noopener noreferrer"&gt;monthly disclosures doubled this year&lt;/a&gt;, from 5,045 in January to 10,740 in August.&lt;/p&gt;

&lt;p&gt;AI is a big part of the story. AI tools now hunt for flaws on their own, and they're good at it. In June, FIRST, the group that forecasts CVE volume each year, said &lt;a href="https://www.first.org/blog/20260615-vulnerability-forecast-update" rel="noopener noreferrer"&gt;AI-assisted discovery made an extreme year likely&lt;/a&gt;. The flaws AI finds tend to be the serious kind, too. Google found that &lt;a href="https://cloud.google.com/blog/topics/threat-intelligence/vulnerability-discovery-and-exploitation-trends-in-the-ai-era" rel="noopener noreferrer"&gt;half of AI-discovered vulnerabilities lead to remote code execution&lt;/a&gt;, against 26% across all CVEs.&lt;/p&gt;

&lt;p&gt;Every one of them can land in a package that sits in one of your images.&lt;/p&gt;

&lt;p&gt;And most teams already carry plenty. Datadog's 2026 report found that &lt;a href="https://www.datadoghq.com/state-of-devsecops/" rel="noopener noreferrer"&gt;87% of organizations run at least one known exploitable vulnerability&lt;/a&gt; in their deployed services. That's not a sign of bad teams. It's what happens when you start from a public base and the packages keep moving.&lt;/p&gt;

&lt;p&gt;They do keep moving. Datadog found that &lt;a href="https://www.datadoghq.com/state-of-devsecops/" rel="noopener noreferrer"&gt;the median dependency is now 278 days behind its latest major version&lt;/a&gt;, up from 215 days a year earlier. Nobody chose to fall behind. Updating the layers under your app is just never the top ticket.&lt;/p&gt;

&lt;h2&gt;
  
  
  Most of the noise isn't the real risk
&lt;/h2&gt;

&lt;p&gt;Here's the part that stings. A lot of what lands in the queue never needed to be there.&lt;/p&gt;

&lt;p&gt;Datadog took every vulnerability with a critical score and added context. Is it running in production? Is it exposed to the internet? Is anyone likely to exploit it? After that, &lt;a href="https://www.datadoghq.com/state-of-devsecops/" rel="noopener noreferrer"&gt;just 18% were still critical&lt;/a&gt;. Less than one in five, the same as the year before.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Of every 100 findings scored critical, about 18 still were once Datadog added context. &lt;a href="https://seeghost.dev/blog/cve-noise/" rel="noopener noreferrer"&gt;See the animated version on the original post.&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Google saw the same thing at a much bigger scale. Of everything disclosed in 2026, &lt;a href="https://cloud.google.com/blog/topics/threat-intelligence/vulnerability-discovery-and-exploitation-trends-in-the-ai-era" rel="noopener noreferrer"&gt;only about 1 in 431 was ever seen being exploited&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;So the real work is finding the few that matter. But to find them, someone still has to sort through all the rest.&lt;/p&gt;

&lt;h2&gt;
  
  
  The bill comes in hours
&lt;/h2&gt;

&lt;p&gt;That sorting isn't free. It comes out of your engineers' week.&lt;/p&gt;

&lt;p&gt;Checkmarx surveyed 2,350 security leaders and developers this year and found that &lt;a href="https://checkmarx.com/blog/just-launched-the-future-of-application-security-in-the-era-of-ai-2027-industry-outlook/" rel="noopener noreferrer"&gt;developers spend nearly half their time, 49%, on security&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Not all of that is base image triage. But a lot of it is the same loop. A scan fails. Someone reads the finding. Someone figures out which layer it lives in. Someone bumps a package, rebuilds, retests and waits for the next scan. Then it happens again next week.&lt;/p&gt;

&lt;p&gt;Try your own numbers. Even small inputs add up fast.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;&lt;a href="https://seeghost.dev/blog/cve-noise/" rel="noopener noreferrer"&gt;Try the hours calculator with your own numbers on the original post.&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Those hours are the ones you hired people to spend on your product. On a platform team, they're the hours that should go to the clusters, the pipelines and the next thing the business asked for.&lt;/p&gt;

&lt;h2&gt;
  
  
  Stop owning the base layer
&lt;/h2&gt;

&lt;p&gt;You can't make the CVE feed slower. You can choose who owns the layers under your app.&lt;/p&gt;

&lt;p&gt;That's what Ghost is for. Ghost is one catalog your whole software factory builds from:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Base images&lt;/strong&gt;, hardened and kept current, so your team isn't patching them by hand.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Language runtimes&lt;/strong&gt; for the services you ship, kept current too.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The top 3,000 packages&lt;/strong&gt; from PyPI, npm and Maven Central.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Signed, with an SBOM&lt;/strong&gt; on every image and package, so security reviews start with answers.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Your engineers stop working through findings in packages they never touched. The findings left in the queue are in your code. That's work worth doing.&lt;/p&gt;

&lt;p&gt;It fits what you already run. Point your Kubernetes deployments and Helm values at Ghost images, or mirror the catalog into Amazon ECR. Your CI/CD keeps working the way it does today. For most services the change is one line:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight docker"&gt;&lt;code&gt;&lt;span class="c"&gt;# before&lt;/span&gt;
&lt;span class="k"&gt;FROM&lt;/span&gt; node:22

&lt;span class="c"&gt;# after&lt;/span&gt;
&lt;span class="k"&gt;FROM&lt;/span&gt; ghost/node:22
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And the price doesn't grow with your image count. Ghost is one flat annual price for your whole organization, with no per-image or per-seat fees.&lt;/p&gt;

&lt;h2&gt;
  
  
  Count the hours first
&lt;/h2&gt;

&lt;p&gt;Before you change anything, find out what the noise costs you now. We'll run a &lt;strong&gt;Ghost Container Economics Assessment&lt;/strong&gt;. We map your images and where they run. We size the CVE work your teams carry today. Then we put it next to a Ghost proposal and prove it on a few of your own images.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://seeghost.dev/#contact" rel="noopener noreferrer"&gt;Ask for an assessment&lt;/a&gt; and pick "A Container Economics Assessment" on the form.&lt;/p&gt;

</description>
      <category>security</category>
      <category>devops</category>
      <category>kubernetes</category>
      <category>containers</category>
    </item>
  </channel>
</rss>
