<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Devopssecurity on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/devopssecurity/</link>
    <description>Recent content in Devopssecurity on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 19 Nov 2026 10:20:34 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/devopssecurity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Skipping CVE‑2026‑1234: a risk‑based patching trade‑off for CI pipelines</title>
      <link>https://linuxeries.org/post/2026-11-19-skipping-cve20261234-a-riskbased-patching-tra/</link>
      <pubDate>Thu, 19 Nov 2026 10:20:34 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-11-19-skipping-cve20261234-a-riskbased-patching-tra/</guid>
      <description>&lt;p&gt;CVE‑2026‑1234 is a privilege‑escalation bug in &lt;em&gt;libfoo&lt;/em&gt; that ships with a lot of Docker‑based CI runners. The advisory gives it a 10‑month CVSS score and calls it “remote code execution” if an attacker can inject a malicious build script. In 2026 most CI services still ship with upstream &lt;em&gt;libfoo&lt;/em&gt; 1.2.3 in their base images, so the patch isn’t in the official repos yet.&lt;/p&gt;&#xA;&lt;p&gt;The real question: &lt;strong&gt;Patch now, or skip it and live with the risk?&lt;/strong&gt; Below is a step‑by‑step risk‑based approach that balances security, build stability, and operational overhead.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
