<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Oxelan Signal — #ingress-nginx</title>
    <link>https://blog.oxelan.com</link>
    <description>Posts tagged ingress-nginx on AI, security and engineering.</description>
    <language>en-us</language>
    <lastBuildDate>Tue, 27 Oct 2026 00:00:00 GMT</lastBuildDate>
    <managingEditor>hello@oxelan.com (Kusal Tharindu)</managingEditor>
    <copyright>© 2026 Oxelan</copyright>
    <atom:link href="https://blog.oxelan.com/tags/ingress-nginx/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>NGINX fixes five flaws, three scored 9.2</title>
      <link>https://blog.oxelan.com/security/nginx-october-2026-cves/</link>
      <guid isPermaLink="true">https://blog.oxelan.com/security/nginx-october-2026-cves/</guid>
      <pubDate>Tue, 27 Oct 2026 00:00:00 GMT</pubDate>
      <description>NGINX 1.30.6 and 1.31.7 close three 9.2 memory bugs, a TLS client-certificate bypass and an HTTP/3 injection path. None is known exploited, and each needs a specific configuration to reach.</description>
      <category>nginx</category>
      <category>ingress-nginx</category>
      <category>kubernetes</category>
      <category>cve</category>
    </item>
  </channel>
</rss>
