<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 10 Oct 2026 21:35:11 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-107813</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-107813</link>
      <description>&lt;p&gt;Nginx UI is a web user interface for the Nginx web server. From 2.0.0 until 2.5.0, the api/cluster router exposes node and namespace mutation operations and cluster-wide Nginx reload or restart operations with AuthRequired but without RequireSecureSession. An authenticated OTP-enabled user possessing a stolen or persisted JWT can therefore perform node CRUD, read or replace node credentials, change namespaces, and invoke nodes/reload_nginx or nodes/restart_nginx without a fresh second-factor step-up. This issue is an incomplete fix for CVE-2026-84315 and is fixed in version 2.5.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nginx UI is a web user interface for the Nginx web server. From 2.0.0 until 2.5.0, the api/cluster router exposes node and namespace mutation operations and cluster-wide Nginx reload or restart operations with AuthRequired but without RequireSecureSession. An authenticated OTP-enabled user possessing a stolen or persisted JWT can therefore perform node CRUD, read or replace node credentials, change namespaces, and invoke nodes/reload_nginx or nodes/restart_nginx without a fresh second-factor step-up. This issue is an incomplete fix for CVE-2026-84315 and is fixed in version 2.5.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-107813</guid>
    </item>
    <item>
      <title>GHSA-h246-wpgf-vmq5 — Nginx UI: Incomplete fix of CVE-2026-84315 - the api/cluster router was not -  wrapped in RequireSecureSession, so thos…</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-h246-wpgf-vmq5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/0xJacky/Nginx-UI&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Incomplete fix of GHSA-5v7c-xpfp-p65m: the secure-session (OTP step-up) requirement added to the nginx, cert, dns, backup, site, and stream mutation routers was not applied to the parallel api/cluster router, so cluster node management and cluster-wide nginx reload/restart run with only a JWT and no step-up. An authenticated user whose JWT is stolen or persisted, but who does not hold a fresh secure-session, can perform cluster node CRUD (including reading and rewriting a node token secret) and trigger cluster-wide nginx reload/restart. Confirmed at HEAD 2cb7ee9102c9d87274de2fa104db804841d140a0.&lt;/p&gt;
&lt;p&gt;## The defect&lt;/p&gt;
&lt;p&gt;GHSA-5v7c-xpfp-p65m required a fresh secure session (an OTP step-up beyond the JWT) for sensitive mutation routes. The fix wrapped the nginx, cert, dns, backup, site, and stream mutation handlers in middleware.RequireSecureSession() and added reload/restart to the MCP sensitive-tool list. It did not touch the physically separate api/cluster package, whose router registers the same class of sensitive operations on the bare authenticated group.&lt;/p&gt;
&lt;p&gt;The fixed sibling, api/nginx/router.go:&lt;/p&gt;
&lt;p&gt;```go
o := r.Group(&amp;#34;&amp;#34;, middleware.RequireSecureSession())   // line 28
{
    o.POST(&amp;#34;nginx/reload&amp;#34;, Reload)                     // line 30
    o.POST(&amp;#34;nginx/restart&amp;#34;, Restart)                   // line 31
}
```&lt;/p&gt;
&lt;p&gt;The missed router, api/cluster/router.go, registers every sensitive operation directly on r with no RequireSecureSession wrapper:&lt;/p&gt;
&lt;p&gt;```go
nodeGroup := r.Group(&amp;#34;nodes&amp;#34;)…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/0xJacky/Nginx-UI&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Incomplete fix of GHSA-5v7c-xpfp-p65m: the secure-session (OTP step-up) requirement added to the nginx, cert, dns, backup, site, and stream mutation routers was not applied to the parallel api/cluster router, so cluster node management and cluster-wide nginx reload/restart run with only a JWT and no step-up. An authenticated user whose JWT is stolen or persisted, but who does not hold a fresh secure-session, can perform cluster node CRUD (including reading and rewriting a node token secret) and trigger cluster-wide nginx reload/restart. Confirmed at HEAD 2cb7ee9102c9d87274de2fa104db804841d140a0.&lt;/p&gt;
&lt;p&gt;## The defect&lt;/p&gt;
&lt;p&gt;GHSA-5v7c-xpfp-p65m required a fresh secure session (an OTP step-up beyond the JWT) for sensitive mutation routes. The fix wrapped the nginx, cert, dns, backup, site, and stream mutation handlers in middleware.RequireSecureSession() and added reload/restart to the MCP sensitive-tool list. It did not touch the physically separate api/cluster package, whose router registers the same class of sensitive operations on the bare authenticated group.&lt;/p&gt;
&lt;p&gt;The fixed sibling, api/nginx/router.go:&lt;/p&gt;
&lt;p&gt;```go
o := r.Group(&amp;#34;&amp;#34;, middleware.RequireSecureSession())   // line 28
{
    o.POST(&amp;#34;nginx/reload&amp;#34;, Reload)                     // line 30
    o.POST(&amp;#34;nginx/restart&amp;#34;, Restart)                   // line 31
}
```&lt;/p&gt;
&lt;p&gt;The missed router, api/cluster/router.go, registers every sensitive operation directly on r with no RequireSecureSession wrapper:&lt;/p&gt;
&lt;p&gt;```go
nodeGroup := r.Group(&amp;#34;nodes&amp;#34;)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-h246-wpgf-vmq5</guid>
    </item>
  </channel>
</rss>
