<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T16:56:58.080743+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/cve-2026-118899</id>
    <title>CVE-2026-118899 — NGINX TLSv1.3 vulnerability</title>
    <updated>2026-11-19T16:56:58.084790+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> F5 NGINX Open Source, F5 NGINX Plus</p>
<p>When using the listen directive with the ssl parameter in the http block with TLSv1.3 enabled, an attacker can use a specially crafted TLS connection to cause an infinite loop in the NGINX worker process while reading the HTTP request body. As a result, the worker process stops accepting new connections and processing existing connections. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.</p>
<p>Impact: This vulnerability allows a remote, unauthenticated attacker to cause a denial-of-service (DoS) of NGINX. There is no control plane exposure; this is a data plane issue only.</p>
<p>Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/cve-2026-118899"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/usn-9159-1</id>
    <title>USN-9159-1 — nginx vulnerabilities</title>
    <updated>2026-11-19T16:56:58.084904+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: nginx, Ubuntu:Pro:16.04:LTS: nginx, Ubuntu:Pro:18.04:LTS: nginx, Ubuntu:Pro:20.04:LTS: nginx, Ubuntu:22.04:LTS: nginx, Ubuntu:24.04:LTS: nginx, Ubuntu:26.10: nginx, Ubuntu:26.04:LTS: nginx</p>
<p>Stephen Fewer and Tomer Schwartz discovered that nginx did not correctly
handle certain memory operations. A remote attacker could possibly use
this issue to cause a denial of service or execute arbitrary code. This
issue only affected Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, Ubuntu 20.04 LTS,
Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 26.04 LTS and Ubuntu 26.10.
(CVE-2026-123007)</p>
<p>Albert Ebb Metnir and Nir Ohfeld discovered that nginx did not correctly
handle certain reusable HTTP/2 connections. A remote attacker could possibly
use this issue to cause a denial of service or execute arbitrary code. This
issue only affected Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, Ubuntu 20.04 LTS,
Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 26.04 LTS and Ubuntu 26.10.
(CVE-2026-123633)</p>
<p>It was discovered that nginx did not correctly handle certain memory
operations. A remote attacker could possibly use this issue to cause a
denial of service or execute arbitrary code. (CVE-2026-113425)</p>
<p>It was discovered that nginx did not correctly handle resolving certain
names or addresses. A remote attacker could possibly use this issue to
cause a denial of service or execute arbitrary code. (CVE-2026-123634)</p>
<p>It was discovered that nginx did not correctly handle certain TLS
connections. A remote attacker could possibly use this issue to cause
a denial of service. This issue only affected Ubuntu 24.04 LTS,
Ubuntu 26.04 LTS and Ubuntu 26.10. (CVE-2026-118899)</p>
<p>It was discovered that nginx did not correctly handle ce…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/usn-9159-1"/>
  </entry>
</feed>
