CVE-2026-6578
CVE-2026-6578 is a medium-severity vulnerability with a CVSS 3.x base score of 5.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-259.
Key facts
- Severity: Medium (CVSS 3.x base score 5.6)
- CVSS v2: 5.1
- CVSS v4: 2.9
- EPSS exploit prediction: 0% (24th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2026-23710
- Weakness: CWE-259
- Published:
- Last modified:
Description
A security flaw has been discovered in liangliangyy DjangoBlog up to 2.1.0.0. This affects an unknown function of the file djangoblog/settings.py of the component Setting Handler. The manipulation of the argument SECRET_KEY results in hard-coded credentials. The attack can be launched remotely. The attack requires a high level of complexity. The exploitability is reported as difficult. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
Frequently asked questions
- What is CVE-2026-6578?
- A security flaw has been discovered in liangliangyy DjangoBlog up to 2.1.0.0. This affects an unknown function of the file djangoblog/settings.py of the component Setting Handler. The manipulation of the argument SECRET_KEY results in hard-coded credentials. The attack can be launched remotely. The attack requires a high level of complexity. The exploitability is reported as difficult. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
- How severe is CVE-2026-6578?
- CVE-2026-6578 has a CVSS 3.x base score of 5.6, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.
- Is CVE-2026-6578 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2026-6578?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2026-6578 have an EU (EUVD) identifier?
- Yes. CVE-2026-6578 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-23710.
- When was CVE-2026-6578 published?
- CVE-2026-6578 was published on 2026-04-19 and last updated on 2026-06-17.
References
- https://github.com/3em0/cve_repo/blob/main/DjangoBlog/Vuln-3-Hardcoded-Django-SECRET_KEY.md
- https://vuldb.com/submit/790283
- https://vuldb.com/vuln/358213
- https://vuldb.com/vuln/358213/cti
Other CWE-259 vulnerabilities
- CVE-2024-32741 — Critical (CVSS 10.0): A vulnerability has been identified in SIMATIC CN 4100 (All versions < V3.0). The affected device contains hard coded…
- CVE-2014-2363 — Critical (CVSS 10.0): Morpho Itemiser 3 8.17 has hardcoded administrative credentials, which makes it easier for remote attackers to obtain…
- CVE-2012-5862 — Critical (CVSS 10.0): These Sinapsi devices store hard-coded passwords in the PHP file of the device. By using the hard-coded passwords in…
- CVE-2025-20286 — Critical (CVSS 9.9): A vulnerability in Amazon Web Services (AWS), Microsoft Azure, and Oracle Cloud Infrastructure (OCI) cloud deployments…
- CVE-2026-35905 — Critical (CVSS 9.8): T3 Technology CPE models T625Pro v1.0.07, T6825G v1.0.03, and T7281 v1.0.03 were discovered to contain a hardcoded…
- CVE-2026-7251 — Critical (CVSS 9.8): Eppendorf BioFlo 320 is vulnerable due to VNC server using a hard-coded password. If a remote attacker knows the…