Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 16 Nov 2026 14:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Kiwi TCMS before 17.1 contains a hard-coded cryptographic key vulnerability that allows remote attackers to forge signed data by using the publicly known Django SECRET_KEY in tcms/settings/common.py. Attackers can forge or tamper with signed cookie-based messages and django.core.signing payloads, weakening password-reset and session-authentication HMACs on deployments keeping the default. | |
| Title | Kiwi TCMS before 17.1 Hard-coded Django SECRET_KEY in Default Settings | |
| First Time appeared |
Kiwitcms
Kiwitcms kiwi Tcms |
|
| Weaknesses | CWE-321 | |
| CPEs | cpe:2.3:a:kiwitcms:kiwi_tcms:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Kiwitcms
Kiwitcms kiwi Tcms |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-11-16T14:19:18.809Z
Reserved: 2026-11-16T12:35:07.027Z
Link: CVE-2026-129882
No data.
No data.
No data.
OpenCVE Enrichment
No data.