<?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://db.gcve.eu</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>Sun, 25 Oct 2026 01:53:48 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-84315</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-84315</link>
      <description>&lt;p&gt;Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.1, Nginx UI does not apply RequireSecureSession to multiple authenticated mutation routes even though OTP-enabled users are expected to present a fresh X-Secure-Session-ID for sensitive actions. A stolen authenticated session can therefore create or alter automatic backups, DNS credentials and records, certificates and ACME users, Nginx control settings, and site or stream automation without completing the OTP or passkey step-up. This issue is fixed in version 2.4.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.1, Nginx UI does not apply RequireSecureSession to multiple authenticated mutation routes even though OTP-enabled users are expected to present a fresh X-Secure-Session-ID for sensitive actions. A stolen authenticated session can therefore create or alter automatic backups, DNS credentials and records, certificates and ACME users, Nginx control settings, and site or stream automation without completing the OTP or passkey step-up. This issue is fixed in version 2.4.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-84315</guid>
    </item>
    <item>
      <title>GHSA-5v7c-xpfp-p65m — Nginx UI OTP secure-session step-up is missing on sensitive mutation routes</title>
      <link>https://db.gcve.eu/vuln/ghsa-5v7c-xpfp-p65m</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/0xJacky/Nginx-UI&lt;/p&gt;
&lt;p&gt;Reporter: Jagadesh Achanta&lt;/p&gt;
&lt;p&gt;Target: `0xJacky/nginx-ui`&lt;/p&gt;
&lt;p&gt;Affected version / commit tested:
- App version: `2.3.10`
- Commit: `4948fba8744e82c3d7003f68ee164e9f49421066`
- Disclosure channel: GitHub Private Vulnerability Reporting
- Credential reference: `cred:github-jagstack-gh-cli`&lt;/p&gt;
&lt;p&gt;## AI assistance disclosure&lt;/p&gt;
&lt;p&gt;This report was prepared by Jagadesh Achanta with assistance from OpenAI/Codex for public source review, local evidence collection, and report drafting.&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Nginx UI has a short-lived OTP/passkey &amp;#34;secure session&amp;#34; step-up boundary for users with 2FA enabled. `RequireSecureSession()` rejects an OTP-enabled user&amp;#39;s request unless the request includes a valid `X-Secure-Session-ID` issued after a fresh OTP/passkey verification.&lt;/p&gt;
&lt;p&gt;The project already applies this step-up middleware to sensitive operations such as:&lt;/p&gt;
&lt;p&gt;- Nginx config create/edit/rename/delete;
- site save/delete/enable/disable/rename/duplicate;
- stream save/delete/enable/disable/rename/duplicate;
- settings save and protected secret reads;
- backup restore.&lt;/p&gt;
&lt;p&gt;However, several similarly sensitive authenticated mutation routes remain outside `RequireSecureSession()`. An attacker who obtains an authenticated JWT/session for a 2FA-enabled user, but does not have the victim&amp;#39;s fresh OTP/passkey secure-session token, can still perform those operations.&lt;/p&gt;
&lt;p&gt;The affected route groups include:&lt;/p&gt;
&lt;p&gt;- automatic backup create/modify/delete/restore/test-S3 operations;
- DNS credential create/edit/delete operations;
- certifi…&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;Reporter: Jagadesh Achanta&lt;/p&gt;
&lt;p&gt;Target: `0xJacky/nginx-ui`&lt;/p&gt;
&lt;p&gt;Affected version / commit tested:
- App version: `2.3.10`
- Commit: `4948fba8744e82c3d7003f68ee164e9f49421066`
- Disclosure channel: GitHub Private Vulnerability Reporting
- Credential reference: `cred:github-jagstack-gh-cli`&lt;/p&gt;
&lt;p&gt;## AI assistance disclosure&lt;/p&gt;
&lt;p&gt;This report was prepared by Jagadesh Achanta with assistance from OpenAI/Codex for public source review, local evidence collection, and report drafting.&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Nginx UI has a short-lived OTP/passkey &amp;#34;secure session&amp;#34; step-up boundary for users with 2FA enabled. `RequireSecureSession()` rejects an OTP-enabled user&amp;#39;s request unless the request includes a valid `X-Secure-Session-ID` issued after a fresh OTP/passkey verification.&lt;/p&gt;
&lt;p&gt;The project already applies this step-up middleware to sensitive operations such as:&lt;/p&gt;
&lt;p&gt;- Nginx config create/edit/rename/delete;
- site save/delete/enable/disable/rename/duplicate;
- stream save/delete/enable/disable/rename/duplicate;
- settings save and protected secret reads;
- backup restore.&lt;/p&gt;
&lt;p&gt;However, several similarly sensitive authenticated mutation routes remain outside `RequireSecureSession()`. An attacker who obtains an authenticated JWT/session for a 2FA-enabled user, but does not have the victim&amp;#39;s fresh OTP/passkey secure-session token, can still perform those operations.&lt;/p&gt;
&lt;p&gt;The affected route groups include:&lt;/p&gt;
&lt;p&gt;- automatic backup create/modify/delete/restore/test-S3 operations;
- DNS credential create/edit/delete operations;
- certifi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-5v7c-xpfp-p65m</guid>
    </item>
  </channel>
</rss>
