Unauthenticated information disclosure via default debug mode
Published Sep 20, 2026 · Updated Sep 20, 2026
Active debug code in aiyiyi121 SxDevOps 1.0 and 1.1 allows remote attackers to read sensitive error details without authentication. backend/sxdevops/settings.py uses true when the DEBUG environment variable is absent, causing Django error pages to return stack traces, local variables, SQL queries, and settings. Exposure requires DEBUG to remain unset and an unauthenticated request to trigger a server error; the disclosed data is limited to details rendered in that response.
Summary
What happened
Active debug code in aiyiyi121 SxDevOps 1.0 and 1.1 allows remote attackers to read sensitive error details without authentication. backend/sxdevops/settings.py uses true when the DEBUG environment variable is absent, causing Django error pages to return stack traces, local variables, SQL queries, and settings. Exposure requires DEBUG to remain unset and an unauthenticated request to trigger a server error; the disclosed data is limited to details rendered in that response.
The record
- CVE
- CVE-2026-93971
- Published
- Sep 20, 2026
- Updated
- Sep 20, 2026
- Vendor
- aiyiyi121
- Product
- SxDevOps
- Classifications
- CWE-200, CWE-284, T1190
- 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?
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