Authentication bypass via hard-coded Django SECRET_KEY
Published Sep 20, 2026 · Updated Sep 20, 2026
Hard-coded cryptographic key in SxDevOps 1.0 and 1.1 allows remote attackers to forge Django-signed data using a known SECRET_KEY. backend/sxdevops/settings.py falls back to a public, fixed SECRET_KEY whenever the environment omits that setting. No authentication is required, but exploitation depends on a reachable feature that trusts Django-signed sessions, tokens, or other data.
Summary
What happened
Hard-coded cryptographic key in SxDevOps 1.0 and 1.1 allows remote attackers to forge Django-signed data using a known SECRET_KEY. backend/sxdevops/settings.py falls back to a public, fixed SECRET_KEY whenever the environment omits that setting. No authentication is required, but exploitation depends on a reachable feature that trusts Django-signed sessions, tokens, or other data.
The record
- CVE
- CVE-2026-93970
- Published
- Sep 20, 2026
- Updated
- Sep 20, 2026
- Vendor
- aiyiyi121
- Product
- SxDevOps
- Classifications
- CWE-798, T1606.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 2026CVE publishedPublication date reported by the CVE source.
- Sep 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0
- Affected versionversion=1.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started