<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security-Patch on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/security-patch/</link><description>Recent content in Security-Patch on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 31 Aug 2026 18:45:38 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/security-patch/index.xml" rel="self" type="application/rss+xml"/><item><title>Argo CD v3.4.8: CVE patches and auto-sync bug fix</title><link>https://curadevops.metacog.co.kr/insights/2026-08-31-v3-4-8/</link><pubDate>Mon, 31 Aug 2026 18:45:38 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-31-v3-4-8/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Teams running Argo CD should schedule an upgrade to 3.4.8 this sprint: it patches three CVEs in UI JS dependencies (none KEV-listed, EPSS ≤ 0.01) and fixes an auto-sync regression that silently skips syncs when a newer commit arrives during an active sync. No hard deadline, but the sync bug is a silent correctness risk on busy clusters.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> Argo CD 3.4 supported · CVE-2026-14257 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-49978 — CISA KEV: not listed, EPSS 0.00 · CVE-2026-59869 — CISA KEV: not listed, EPSS 0.01&lt;/li>
&lt;/ul></description></item><item><title>GitLab critical patch release: 19.2.4, 19.1.6, 19.0.8, 18.11.11</title><link>https://curadevops.metacog.co.kr/insights/2026-08-18-gitlab-critical-patch-release-19-2-4-19-1-6-19-0-8-18-11-11/</link><pubDate>Tue, 18 Aug 2026 11:17:30 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-08-18-gitlab-critical-patch-release-19-2-4-19-1-6-19-0-8-18-11-11/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> If running a self-managed GitLab instance, upgrade to the patched version in your release line; no public PoC or KEV listing is confirmed from the title alone, so this is urgent-but-scheduled rather than emergency.&lt;/li>
&lt;li>&lt;strong>CI/CD — Act:&lt;/strong> GitLab CI users on self-managed instances should upgrade to 19.2.4, 19.1.6, 19.0.8, or 18.11.11 promptly — a critical patch to the CI/CD platform itself can directly break or compromise pipelines and should be treated as an outage-level priority.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> major release (19.0)&lt;/li>
&lt;/ul></description></item><item><title>OpenTofu v1.12.5: ECH privacy-leak security fix and provider-state bug fix</title><link>https://curadevops.metacog.co.kr/insights/2026-07-27-v1-12-5/</link><pubDate>Mon, 27 Jul 2026 14:28:32 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-07-27-v1-12-5/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Platform engineers running OpenTofu should upgrade to 1.12.5 to address the ECH handshake privacy leak (server hostname de-anonymization via passive observation) and the implicit-move provider state bug; no KEV listing or active exploitation reported, so no hard deadline, but this should be included in the next IaC toolchain update cycle.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>