cve.bz

CVE-2026-105392 lybbn django-vue-lyadmin: Key Management Errors

5.5 mediumEPSS 0.3%

Medium (5.5) in lybbn django-vue-lyadmin. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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."

Severity

CVSS 4.0

5.5 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

CVSS 3.1

7.3 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-320 Key Management Errors
CWE-321 Use of Hard-coded Cryptographic Key
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-105392 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105392?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105392?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105392 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Lybbn Django-Vue-Lyadmin3.2.0
Lybbn Django-Vue-Lyadmin3.2.1
Lybbn Django-Vue-Lyadmin3.2.2
Lybbn Django-Vue-Lyadmin3.2.3
Lybbn Django-Vue-Lyadmin3.2.4
Lybbn Django-Vue-Lyadmin3.2.5
Lybbn Django-Vue-Lyadmin3.2.6
Lybbn Django-Vue-Lyadmin3.2.7
Lybbn Django-Vue-Lyadmin3.2.8
Lybbn Django-Vue-Lyadmin3.2.9
Lybbn Django-Vue-Lyadmin3.2.10
Lybbn Django-Vue-Lyadmin3.2.11
Lybbn Django-Vue-Lyadmin3.2.12

References

Check your stackJSON