<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CVE-2025-1974 - 标签 - Shengxu · 云架构 &amp; DevOps</title><link>https://shengxu.pages.dev/tags/cve-2025-1974/</link><description>Shengxu 的云架构 &amp; DevOps 技术博客：Kubernetes、Cilium、可观测性、LLM 基础设施、Agent 工程化等。</description><generator>Hugo 0.153.2 &amp; FixIt v0.4.0-alpha.3-20251225101113-8ffb9a95</generator><language>zh-CN</language><lastBuildDate>Sat, 27 Dec 2025 10:00:00 +0800</lastBuildDate><atom:link href="https://shengxu.pages.dev/tags/cve-2025-1974/index.xml" rel="self" type="application/rss+xml"/><item><title>IngressNightmare (CVE-2025-1974)：漏洞详解与 Gateway API 迁移指南</title><link>https://shengxu.pages.dev/posts/ingress-nightmare-gateway-api-migration/</link><pubDate>Sat, 27 Dec 2025 10:00:00 +0800</pubDate><guid>https://shengxu.pages.dev/posts/ingress-nightmare-gateway-api-migration/</guid><category domain="https://shengxu.pages.dev/categories/kubernetes/">Kubernetes</category><category domain="https://shengxu.pages.dev/categories/security/">Security</category><description>&lt;p&gt;最近曝光的 Ingress-NGINX &lt;strong&gt;“IngressNightmare”&lt;/strong&gt; 漏洞，把 nginx‑ingress 再次推上风口浪尖，也给还停留在传统 Ingress 的集群敲了警钟。&lt;/p&gt;
&lt;p&gt;下面从漏洞回顾、风险分析、短期修补，到如何借机迁移到 Gateway API，以及迁移前后的优劣对比，做一篇面向工程实践的技术梳理。&lt;/p&gt;</description></item></channel></rss>