<?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, 20 Oct 2026 17:35:03 +0000</lastBuildDate>
    <item>
      <title>PYSEC-2026-2593 — LightRAG: Hardcoded JWT Signing Secret Allows Authentication Bypass</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-2593</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: lightrag-hku&lt;/p&gt;
&lt;p&gt;Subject: Security Vulnerability Report Hardcoded JWT Secret (CVE-2026-30762)&lt;/p&gt;
&lt;p&gt;Hi HKUDS team,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m writing to report a security vulnerability I discovered in LightRAG v1.4.10. This has been assigned CVE-2026-30762 by MITRE.&lt;/p&gt;
&lt;p&gt;Vulnerability: Hardcoded JWT signing secret
Type: Improper Authentication (CWE-287)
Severity: High
Attack Vector: Remote / Unauthenticated&lt;/p&gt;
&lt;p&gt;Summary:
The file lightrag/api/config.py (line 397) uses a default JWT secret &amp;#34;lightrag-jwt-default-secret&amp;#34; when the TOKEN_SECRET environment variable is not set. The AuthHandler in lightrag/api/auth.py (lines 24-25) uses this secret to sign and verify tokens. An unauthenticated attacker can forge valid JWT tokens using the publicly known default secret and gain access to any protected endpoint.&lt;/p&gt;
&lt;p&gt;Reproduction:
1. Install LightRAG v1.4.10 with AUTH_ACCOUNTS configured but no TOKEN_SECRET set
2. Use PyJWT to sign a token: jwt.encode({&amp;#34;sub&amp;#34;: &amp;#34;admin&amp;#34;, &amp;#34;role&amp;#34;: &amp;#34;user&amp;#34;}, &amp;#34;lightrag-jwt-default-secret&amp;#34;, algorithm=&amp;#34;HS256&amp;#34;)
3. Send a request to any protected endpoint with the header: Authorization: Bearer &amp;lt;forged_token&amp;gt;
4. Access is granted without valid credentials&lt;/p&gt;
&lt;p&gt;Suggested Fix:
Require TOKEN_SECRET to be explicitly set when AUTH_ACCOUNTS is configured. Refuse to start the API server if authentication is enabled but no custom secret is provided.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m following a 90-day responsible disclosure timeline from today&amp;#39;s date. Please let me know if you have any questions or need additional information.&lt;/p&gt;
&lt;p&gt;Best regards,
Venkata Avinash…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: lightrag-hku&lt;/p&gt;
&lt;p&gt;Subject: Security Vulnerability Report Hardcoded JWT Secret (CVE-2026-30762)&lt;/p&gt;
&lt;p&gt;Hi HKUDS team,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m writing to report a security vulnerability I discovered in LightRAG v1.4.10. This has been assigned CVE-2026-30762 by MITRE.&lt;/p&gt;
&lt;p&gt;Vulnerability: Hardcoded JWT signing secret
Type: Improper Authentication (CWE-287)
Severity: High
Attack Vector: Remote / Unauthenticated&lt;/p&gt;
&lt;p&gt;Summary:
The file lightrag/api/config.py (line 397) uses a default JWT secret &amp;#34;lightrag-jwt-default-secret&amp;#34; when the TOKEN_SECRET environment variable is not set. The AuthHandler in lightrag/api/auth.py (lines 24-25) uses this secret to sign and verify tokens. An unauthenticated attacker can forge valid JWT tokens using the publicly known default secret and gain access to any protected endpoint.&lt;/p&gt;
&lt;p&gt;Reproduction:
1. Install LightRAG v1.4.10 with AUTH_ACCOUNTS configured but no TOKEN_SECRET set
2. Use PyJWT to sign a token: jwt.encode({&amp;#34;sub&amp;#34;: &amp;#34;admin&amp;#34;, &amp;#34;role&amp;#34;: &amp;#34;user&amp;#34;}, &amp;#34;lightrag-jwt-default-secret&amp;#34;, algorithm=&amp;#34;HS256&amp;#34;)
3. Send a request to any protected endpoint with the header: Authorization: Bearer &amp;lt;forged_token&amp;gt;
4. Access is granted without valid credentials&lt;/p&gt;
&lt;p&gt;Suggested Fix:
Require TOKEN_SECRET to be explicitly set when AUTH_ACCOUNTS is configured. Refuse to start the API server if authentication is enabled but no custom secret is provided.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m following a 90-day responsible disclosure timeline from today&amp;#39;s date. Please let me know if you have any questions or need additional information.&lt;/p&gt;
&lt;p&gt;Best regards,
Venkata Avinash…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-2593</guid>
    </item>
  </channel>
</rss>
