<?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 12:25:08 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-354535</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-354535</link>
      <description>EUVD-2026-354535</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-354535</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64859</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-64859</link>
      <description>&lt;p&gt;New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to 1.0.0-rc.7, the admin user list and user lookup APIs, including GET /api/user/, return User.AccessToken as access_token because User model objects are serialized after queries use Omit(&amp;#34;password&amp;#34;), allowing an authenticated administrator to obtain the root user&amp;#39;s bearer token and access root-only system configuration APIs. This issue is fixed in version 1.0.0-rc.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to 1.0.0-rc.7, the admin user list and user lookup APIs, including GET /api/user/, return User.AccessToken as access_token because User model objects are serialized after queries use Omit(&amp;#34;password&amp;#34;), allowing an authenticated administrator to obtain the root user&amp;#39;s bearer token and access root-only system configuration APIs. This issue is fixed in version 1.0.0-rc.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-64859</guid>
    </item>
    <item>
      <title>GHSA-6x2c-phff-wx57 — New API: User List API Leaks Root User Access Token Leading to Privilege Escalation</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6x2c-phff-wx57</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/QuantumNous/new-api&lt;/p&gt;
&lt;p&gt;## Vulnerability Information&lt;/p&gt;
&lt;p&gt;- **Product**: new-api
- **Affected versions**: versions before `v1.0.0-rc.7` that serialize `User.AccessToken` as `access_token`; the issue was confirmed in `v0.12.14`
- **Patched version**: `v1.0.0-rc.7`
- **Fixed commit**: `0936e2504655a5cbf7bc3c388f6d3e2bb24916d3`
- **Type**: Information Disclosure / Privilege Escalation&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;In affected versions of new-api, the admin user list and user lookup APIs can return the `access_token` field for users, including the root user. An authenticated admin user can call endpoints such as `GET /api/user/` to retrieve user records. Because access tokens function as bearer credentials for API authentication, leaking the root user&amp;#39;s access token allows an admin user to authenticate as root and access root-only endpoints such as system configuration APIs.&lt;/p&gt;
&lt;p&gt;This bypasses the intended role boundary between admin users and the root user and can result in privilege escalation to full system control.&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;The `User.AccessToken` field was serialized as `json:&amp;#34;access_token&amp;#34;` in affected versions. User management APIs returned `User` model objects directly after omitting only the password field from database queries, so JSON serialization could include `access_token` in API responses.&lt;/p&gt;
&lt;p&gt;Affected code patterns include user list, user search, and user detail paths that use `Omit(&amp;#34;password&amp;#34;)` without preventing `access_token` from being serialized.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;- An authenticated admin user may obtain…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/QuantumNous/new-api&lt;/p&gt;
&lt;p&gt;## Vulnerability Information&lt;/p&gt;
&lt;p&gt;- **Product**: new-api
- **Affected versions**: versions before `v1.0.0-rc.7` that serialize `User.AccessToken` as `access_token`; the issue was confirmed in `v0.12.14`
- **Patched version**: `v1.0.0-rc.7`
- **Fixed commit**: `0936e2504655a5cbf7bc3c388f6d3e2bb24916d3`
- **Type**: Information Disclosure / Privilege Escalation&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;In affected versions of new-api, the admin user list and user lookup APIs can return the `access_token` field for users, including the root user. An authenticated admin user can call endpoints such as `GET /api/user/` to retrieve user records. Because access tokens function as bearer credentials for API authentication, leaking the root user&amp;#39;s access token allows an admin user to authenticate as root and access root-only endpoints such as system configuration APIs.&lt;/p&gt;
&lt;p&gt;This bypasses the intended role boundary between admin users and the root user and can result in privilege escalation to full system control.&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;The `User.AccessToken` field was serialized as `json:&amp;#34;access_token&amp;#34;` in affected versions. User management APIs returned `User` model objects directly after omitting only the password field from database queries, so JSON serialization could include `access_token` in API responses.&lt;/p&gt;
&lt;p&gt;Affected code patterns include user list, user search, and user detail paths that use `Omit(&amp;#34;password&amp;#34;)` without preventing `access_token` from being serialized.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;- An authenticated admin user may obtain…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6x2c-phff-wx57</guid>
    </item>
  </channel>
</rss>
