CVE-2026-129882: Kiwi TCMS before 17.1 Hard-coded Django SECRET_KEY in Default Settings
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 SECRETKEY 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.
Affected Software
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Kiwi TCMS deployments before 17.1 that retain the default Django SECRET_KEY are exposed. Deployments using a separately configured, non-public secret key are not identified as affected by the provided information.
What does an attacker need to exploit it?
An attacker can exploit the issue remotely without authentication by using the publicly known default key. Successful exploitation requires the target to be using that default key.
What can an attacker do with the known key?
An attacker can forge or tamper with signed cookie-based messages and django.core.signing payloads. The issue also weakens HMAC protections associated with password resets and session authentication.
What should be done if upgrading is not immediately possible?
Replace the default Django SECRET_KEY with a unique secret key so the publicly known key cannot be used to forge signed data. Upgrade to Kiwi TCMS 17.1 when possible.