# CVE-2026-105392: Lybbn Django-Vue-Lyadmin JWT Signing settings.py hard-coded key

> Attackers can exploit a hard-coded JWT signing key in Django-Vue-Lyadmin to bypass authentication and potentially take over accounts.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-5gfh-7q6r-6q5p

## What is CVE-2026-105392?

CVE-2026-105392 is a medium-severity vulnerability in Lybbn Django-Vue-Lyadmin, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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."

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key), CWE-320

## Which versions are affected by CVE-2026-105392?


## How do I fix CVE-2026-105392?

No fix has been published for CVE-2026-105392 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105392 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105392 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105392 and fix it if it is affected.

What it is: CVE-2026-105392 is a medium-severity vulnerability in Lybbn Django-Vue-Lyadmin, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105392 exists.

Affected product: Lybbn Django-Vue-Lyadmin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105392/ (Markdown: https://insights.sbomify.com/CVE-2026-105392/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105392
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105392
- OSV: https://osv.dev/vulnerability/CVE-2026-105392

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105392/
Summaries are generated and may contain mistakes; the official description above is the record.