Hard-coded JWT signing key in Lybbn Django-Vue-Lyadmin
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · Low · Low
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-321.
Summary
Lybbn Django-Vue-Lyadmin up to 3.2.12 uses a hard-coded cryptographic key for JWT signing in backend/application/settings.py (CWE-321). An unauthenticated remote attacker can exploit this flaw, and a public exploit has been disclosed and may be used.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Description from the CNA
A vulnerability has been found in Lybbn Django-Vue-Lyadmin up to 3.2.12. The impacted element is an unknown function of the file backend/application/settings.py of the component JWT Signing. The manipulation of the argument SECRET_KEY leads to use of hard-coded cryptographic key . Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used. The project maintainer explains: "The issue with this key is described in the documentation. Developers need to manually change their keys before deployment."
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Lybbn | Django-Vue-Lyadmin | 3.2.0; 3.2.1; 3.2.2; 3.2.3; 3.2.4; 3.2.5; 3.2.6; 3.2.7; 3.2.8; 3.2.9; 3.2.10; 3.2.11; 3.2.12 | — | No fix listed | CNA |
- Django-Vue-Lyadmin VendorLybbn Affected 3.2.0; 3.2.1; 3.2.2; 3.2.3; 3.2.4; 3.2.5; 3.2.6; 3.2.7; 3.2.8; 3.2.9; 3.2.10; 3.2.11; 3.2.12 Fixed in — No fix listed CNA
Remediation
The sources list no fixed version for Lybbn Django-Vue-Lyadmin. The project maintainer states that developers must manually change the SECRET_KEY before deployment.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Timeline
- 2026-10-06 Threatist record created from CVE-2026-105392
- 2026-10-06 Alias added: GHSA-5gfh-7q6r-6q5p
- 2026-10-06 CISA SSVC decision points changed
- 2026-10-06 Priority changed: MEDIUM → HIGH
References
Sources
- CVE-2026-105392 · CVE Program
- CVE-2026-105392 · NVD
- FIRST EPSS
- GHSA-5gfh-7q6r-6q5p · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences