KIWI TCMS · CVE-2026-129882 · Other
NO FIX YET · SEE WHAT TO DO
Kiwi TCMS before 17.1 ships a hard-coded Django SECRET_KEY in tcms/settings/common.py, and that key is publicly known. An attacker can forge or tamper with signed cookies and django.core.signing payloads, which weakens password-reset and session HMACs on deployments that keep the default.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Self-hosted Kiwi TCMS deployments before 17.1 that keep the default SECRET_KEY from tcms/settings/common.py are exposed. Teams that have set their own secret key, or that run a patched version, are not affected by the forgery described in the sources.
Not affected if custom-secret-key
Who cares django, kiwi-tcms, self-hosted
tcms/settings/common.py in the deployed Kiwi TCMS code and check whether SECRET_KEY is still the bundled default value.17.1 are affected.17.1 or later.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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.