<?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>Wed, 07 Oct 2026 01:39:22 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-338612</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-338612</link>
      <description>EUVD-2026-338612</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-338612</guid>
    </item>
    <item>
      <title>fkie_cve-2026-55445</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-55445</link>
      <description>&lt;p&gt;Qinglong is a timed task management platform supporting Python3, JavaScript, Shell, and Typescript. Prior to 2.20.1, the init guard middleware in back/loaders/express.ts checks /api/user/init but not /open/user/init, while rewrite(&amp;#39;/open/*&amp;#39;, &amp;#39;/api/$1&amp;#39;) rewrites the whitelisted /open/* path after JWT authentication and the guard have passed; an unauthenticated attacker can send PUT /open/user/init to reset administrator credentials on an initialized instance. This issue is fixed in 2.20.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Qinglong is a timed task management platform supporting Python3, JavaScript, Shell, and Typescript. Prior to 2.20.1, the init guard middleware in back/loaders/express.ts checks /api/user/init but not /open/user/init, while rewrite(&amp;#39;/open/*&amp;#39;, &amp;#39;/api/$1&amp;#39;) rewrites the whitelisted /open/* path after JWT authentication and the guard have passed; an unauthenticated attacker can send PUT /open/user/init to reset administrator credentials on an initialized instance. This issue is fixed in 2.20.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-55445</guid>
    </item>
    <item>
      <title>GHSA-v667-gc2r-2xm7 — Qinglong has an incomplete fix for CVE-2026-3965: Improper Authentication</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-v667-gc2r-2xm7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @whyour/qinglong&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The init guard middleware in Qinglong only checks `/api/user/init` paths but not `/open/user/init`, which is whitelisted from JWT authentication and rewritten to `/api/user/init` after the guard has already passed, allowing unauthenticated admin credential reset on initialized instances.&lt;/p&gt;
&lt;p&gt;### Affected Package&lt;/p&gt;
&lt;p&gt;- **Ecosystem:** npm
- **Package:** whyour/qinglong
- **Affected versions:** &amp;lt; 6bec52dca158
- **Patched versions:** &amp;gt;= 6bec52dca158&lt;/p&gt;
&lt;p&gt;### Severity&lt;/p&gt;
&lt;p&gt;Medium&lt;/p&gt;
&lt;p&gt;### CWE&lt;/p&gt;
&lt;p&gt;CWE-287 — Improper Authentication&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The Qinglong panel has an initialization endpoint (`/api/user/init`) that allows setting admin credentials. Once the system is initialized, an init guard middleware is supposed to block further calls. The middleware in `back/loaders/express.ts` only checks:&lt;/p&gt;
&lt;p&gt;```javascript
![&amp;#39;/api/user/init&amp;#39;, &amp;#39;/api/user/notification/init&amp;#39;].includes(pathLower)
```&lt;/p&gt;
&lt;p&gt;However, the application also has a URL rewrite rule: `rewrite(&amp;#39;/open/*&amp;#39;, &amp;#39;/api/$1&amp;#39;)`. The `/open/*` paths are whitelisted from JWT authentication.&lt;/p&gt;
&lt;p&gt;The middleware ordering creates the bypass: first, JWT auth sees `/open/*` paths match the whitelist regex and skips authentication. Second, the init guard only checks for `/api/user/init` -- `/open/user/init` passes through as &amp;#34;not an init path&amp;#34;. Third, the URL rewrite transforms `/open/user/init` to `/api/user/init` after the guard has already passed.&lt;/p&gt;
&lt;p&gt;This means an unauthenticated attacker can send `PUT /open/user/init` with new credentials to reset the adm…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @whyour/qinglong&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The init guard middleware in Qinglong only checks `/api/user/init` paths but not `/open/user/init`, which is whitelisted from JWT authentication and rewritten to `/api/user/init` after the guard has already passed, allowing unauthenticated admin credential reset on initialized instances.&lt;/p&gt;
&lt;p&gt;### Affected Package&lt;/p&gt;
&lt;p&gt;- **Ecosystem:** npm
- **Package:** whyour/qinglong
- **Affected versions:** &amp;lt; 6bec52dca158
- **Patched versions:** &amp;gt;= 6bec52dca158&lt;/p&gt;
&lt;p&gt;### Severity&lt;/p&gt;
&lt;p&gt;Medium&lt;/p&gt;
&lt;p&gt;### CWE&lt;/p&gt;
&lt;p&gt;CWE-287 — Improper Authentication&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The Qinglong panel has an initialization endpoint (`/api/user/init`) that allows setting admin credentials. Once the system is initialized, an init guard middleware is supposed to block further calls. The middleware in `back/loaders/express.ts` only checks:&lt;/p&gt;
&lt;p&gt;```javascript
![&amp;#39;/api/user/init&amp;#39;, &amp;#39;/api/user/notification/init&amp;#39;].includes(pathLower)
```&lt;/p&gt;
&lt;p&gt;However, the application also has a URL rewrite rule: `rewrite(&amp;#39;/open/*&amp;#39;, &amp;#39;/api/$1&amp;#39;)`. The `/open/*` paths are whitelisted from JWT authentication.&lt;/p&gt;
&lt;p&gt;The middleware ordering creates the bypass: first, JWT auth sees `/open/*` paths match the whitelist regex and skips authentication. Second, the init guard only checks for `/api/user/init` -- `/open/user/init` passes through as &amp;#34;not an init path&amp;#34;. Third, the URL rewrite transforms `/open/user/init` to `/api/user/init` after the guard has already passed.&lt;/p&gt;
&lt;p&gt;This means an unauthenticated attacker can send `PUT /open/user/init` with new credentials to reset the adm…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-v667-gc2r-2xm7</guid>
    </item>
  </channel>
</rss>
