CVE-2026-129882
Kiwi TCMS before 17.1 contains a hard-coded cryptographic key …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/kiwitcms/kiwitcms/blob/v17.0/tcms/settings/common.py#L24-L25
- github.com/kiwitcms/kiwitcms/commit/ae58d71662284b0da5fb3d2228f77ac16842139a
- github.com/kiwitcms/kiwitcms/releases/tag/v17.1
- github.com/kiwitcms/kiwitcms/security/advisories/GHSA-m9h5-c637-cpcg
- www.vulncheck.com/advisories/kiwi-tcms-before-17.1-hard-coded-django-secret-key-in-default
- nvd.nist.gov/vuln/detail/CVE-2026-129882
- cve.org/CVERecord?id=CVE-2026-129882
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.