CVE-2026-129882 Kiwi TCMS before 17.1 Hard-coded Django SECRET_KEY in Default Settings
Remote attackers can forge signed cookies and password-reset tokens using Kiwi TCMS's default Django SECRET_KEY, weakening authentication.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Harmful if only installed
- Yes
- Needs a specific call
- No
- Fix
- None listed
What is CVE-2026-129882?
CVE-2026-129882 is a medium-severity hardcoded credentials vulnerability in Kiwi TCMS, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-321
Which versions are affected by CVE-2026-129882?
1 open source package ship an affected version, including kiwitcms/kiwitcms.
Having an affected version installed is enough. The problem is in what it ships or how it installs, so no code has to call it.
| Package | Affected | Fixed in |
|---|---|---|
kiwitcms/kiwitcms GitHubpkg:github/kiwitcms/kiwitcms | All versions | 17.1 |
How do I fix CVE-2026-129882?
Upgrade kiwitcms/kiwitcms to 17.1 or later.
Upgrade, then change or revoke the exposed credential wherever it is used. More about Hardcoded credentials.
Is CVE-2026-129882 being exploited?
There is no known exploitation of CVE-2026-129882 in the wild and no public exploit code.
Sources
Also known as GHSA-m5q7-m9q7-pwmp, GHSA-m9h5-c637-cpcg.