HKUDS LightRAG up to 1.4.13 API decode signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in HKUDS LightRAG up to 1.4.13. Impacted is the function decode of the component API. The manipulation results in signature verification.
This vulnerability is cataloged as CVE-2026-39413. The attack may be launched remotely. There is no exploit available.
The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in HKUDS LightRAG up to 1.4.13. Affected is the function decode of the component API. The manipulation with an unknown input leads to a signature verification vulnerability. CWE is classifying the issue as CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. This is going to have an impact on confidentiality. CVE summarizes:
LightRAG provides simple and fast retrieval-augmented generation. Prior to 1.4.14, the LightRAG API is vulnerable to a JWT algorithm confusion attack where an attacker can forge tokens by specifying 'alg': 'none' in the JWT header. Since the jwt.decode() call does not explicitly deny the 'none' algorithm, a crafted token without a signature will be accepted as valid, leading to unauthorized access. This vulnerability is fixed in 1.4.14.
The advisory is available at github.com. This vulnerability is traded as CVE-2026-39413 since 04/07/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. Additional levels of successful authentication are needed for exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.
Upgrading to version 1.4.14 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
Website
- Product: https://github.com/HKUDS/LightRAG/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.1VulDB Meta Temp Score: 3.0
VulDB Base Score: 2.0
VulDB Temp Score: 1.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.2
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Signature verificationCWE: CWE-347 / CWE-345
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: LightRAG 1.4.14
Timeline
04/07/2026 CVE reserved04/09/2026 Advisory disclosed
04/09/2026 VulDB entry created
04/09/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-8ffj-4hx4-9pgf
Status: Confirmed
CVE: CVE-2026-39413 (🔒)
GCVE (CVE): GCVE-0-2026-39413
GCVE (VulDB): GCVE-100-356394
Entry
Created: 04/09/2026 02:14Changes: 04/09/2026 02:14 (65)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.