<?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://cve.radiocsirt.org</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>Tue, 06 Oct 2026 10:48:09 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-372930</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-372930</link>
      <description>EUVD-2026-372930</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-372930</guid>
    </item>
    <item>
      <title>fkie_cve-2026-61628</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-61628</link>
      <description>&lt;p&gt;nginx ignition is a user interface for the nginx web server. Prior to version 2.41.1, `POST /api/users/onboarding/finish` is registered as anonymous (unauthenticated) and creates a user with full ReadWrite admin permissions. Because the handler uses a check-then-act (TOCTOU) pattern between the &amp;#34;onboarding already completed?&amp;#34; check and the user-creation write, with no atomic guard, a remote unauthenticated attacker who can reach an instance in its pre-onboarding state can create an administrator account for themselves — and concurrent requests can create multiple admin accounts in a single race. Version 2.41.1 patches the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;nginx ignition is a user interface for the nginx web server. Prior to version 2.41.1, `POST /api/users/onboarding/finish` is registered as anonymous (unauthenticated) and creates a user with full ReadWrite admin permissions. Because the handler uses a check-then-act (TOCTOU) pattern between the &amp;#34;onboarding already completed?&amp;#34; check and the user-creation write, with no atomic guard, a remote unauthenticated attacker who can reach an instance in its pre-onboarding state can create an administrator account for themselves — and concurrent requests can create multiple admin accounts in a single race. Version 2.41.1 patches the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-61628</guid>
    </item>
    <item>
      <title>GHSA-pxcx-fv34-x9p5 — nginx ignition has Unauthenticated Admin Account Creation via Onboarding Race Condition</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pxcx-fv34-x9p5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/lucasdillmann/nginx-ignition&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`POST /api/users/onboarding/finish` is registered as **anonymous (unauthenticated)** and creates a user with **full ReadWrite admin permissions**. Because the handler uses a check-then-act (TOCTOU) pattern between the &amp;#34;onboarding already completed?&amp;#34; check and the user-creation write, with no atomic guard, a remote unauthenticated attacker who can reach an instance in its pre-onboarding state can create an administrator account for themselves — and concurrent requests can create multiple admin accounts in a single race.&lt;/p&gt;
&lt;p&gt;## Affected component&lt;/p&gt;
&lt;p&gt;- Endpoint: `POST /api/users/onboarding/finish`
- Route registration: `api/user/routes.go:49` → `authorizer.AllowAnonymous(http.MethodPost, &amp;#34;/api/users/onboarding/finish&amp;#34;)`
- Handler: `api/user/onboarding_finish_handler.go`&lt;/p&gt;
&lt;p&gt;## Technical details&lt;/p&gt;
&lt;p&gt;The route is explicitly allowed without authentication:&lt;/p&gt;
&lt;p&gt;```go
// api/user/routes.go:48-49
authorizer.AllowAnonymous(http.MethodGet,  &amp;#34;/api/users/onboarding/status&amp;#34;)
authorizer.AllowAnonymous(http.MethodPost, &amp;#34;/api/users/onboarding/finish&amp;#34;)
```&lt;/p&gt;
&lt;p&gt;The handler reads the onboarding state, returns 403 if already finished, and otherwise creates a user with every permission set to ReadWrite:&lt;/p&gt;
&lt;p&gt;```go
// api/user/onboarding_finish_handler.go
func (h onboardingFinishHandler) handle(ctx *gin.Context) {
    alreadyFinished, err := h.commands.OnboardingCompleted(ctx.Request.Context())  // (1) CHECK
    if err != nil { panic(err) }
    if alreadyFinished {
        ctx.Status(http.StatusForbidden)…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/lucasdillmann/nginx-ignition&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`POST /api/users/onboarding/finish` is registered as **anonymous (unauthenticated)** and creates a user with **full ReadWrite admin permissions**. Because the handler uses a check-then-act (TOCTOU) pattern between the &amp;#34;onboarding already completed?&amp;#34; check and the user-creation write, with no atomic guard, a remote unauthenticated attacker who can reach an instance in its pre-onboarding state can create an administrator account for themselves — and concurrent requests can create multiple admin accounts in a single race.&lt;/p&gt;
&lt;p&gt;## Affected component&lt;/p&gt;
&lt;p&gt;- Endpoint: `POST /api/users/onboarding/finish`
- Route registration: `api/user/routes.go:49` → `authorizer.AllowAnonymous(http.MethodPost, &amp;#34;/api/users/onboarding/finish&amp;#34;)`
- Handler: `api/user/onboarding_finish_handler.go`&lt;/p&gt;
&lt;p&gt;## Technical details&lt;/p&gt;
&lt;p&gt;The route is explicitly allowed without authentication:&lt;/p&gt;
&lt;p&gt;```go
// api/user/routes.go:48-49
authorizer.AllowAnonymous(http.MethodGet,  &amp;#34;/api/users/onboarding/status&amp;#34;)
authorizer.AllowAnonymous(http.MethodPost, &amp;#34;/api/users/onboarding/finish&amp;#34;)
```&lt;/p&gt;
&lt;p&gt;The handler reads the onboarding state, returns 403 if already finished, and otherwise creates a user with every permission set to ReadWrite:&lt;/p&gt;
&lt;p&gt;```go
// api/user/onboarding_finish_handler.go
func (h onboardingFinishHandler) handle(ctx *gin.Context) {
    alreadyFinished, err := h.commands.OnboardingCompleted(ctx.Request.Context())  // (1) CHECK
    if err != nil { panic(err) }
    if alreadyFinished {
        ctx.Status(http.StatusForbidden)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pxcx-fv34-x9p5</guid>
    </item>
    <item>
      <title>Withdrawn: UBUNTU-CVE-2026-61628</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-61628</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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.04:LTS: nginx&lt;/p&gt;
&lt;p&gt;nginx ignition is a user interface for the nginx web server. Prior to version 2.41.1, `POST /api/users/onboarding/finish` is registered as anonymous (unauthenticated) and creates a user with full ReadWrite admin permissions. Because the handler uses a check-then-act (TOCTOU) pattern between the &amp;#34;onboarding already completed?&amp;#34; check and the user-creation write, with no atomic guard, a remote unauthenticated attacker who can reach an instance in its pre-onboarding state can create an administrator account for themselves — and concurrent requests can create multiple admin accounts in a single race. Version 2.41.1 patches the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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.04:LTS: nginx&lt;/p&gt;
&lt;p&gt;nginx ignition is a user interface for the nginx web server. Prior to version 2.41.1, `POST /api/users/onboarding/finish` is registered as anonymous (unauthenticated) and creates a user with full ReadWrite admin permissions. Because the handler uses a check-then-act (TOCTOU) pattern between the &amp;#34;onboarding already completed?&amp;#34; check and the user-creation write, with no atomic guard, a remote unauthenticated attacker who can reach an instance in its pre-onboarding state can create an administrator account for themselves — and concurrent requests can create multiple admin accounts in a single race. Version 2.41.1 patches the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-61628</guid>
    </item>
  </channel>
</rss>
