Skip to main content
CVE-2026-129882VulnerabilityPublished

Kiwi TCMS before 17.1 contains a hard-coded cryptographic key vulnerability that allows remote attackers to forge

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-129882· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 17.1 when convenient.

Data as of 16 Nov 2026, 17:04 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.3
CNA (VulnCheck)CVSS 3.14.8
Patch
Available – fixed in 17.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade Kiwi TCMS to 17.1.

Affected software

ProductAffectedFixed in
Kiwi TCMSKiwi TCMSAffected
  • <17.1
Fixed in
  • 17.1
GitHubKiwi TCMSpkg:github/Kiwi TCMSOther threatsAffected
  • <17.1
Fixed in
  • 17.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Kiwi TCMS to version 17.1 or later where this vulnerability is addressed. Deployments must replace the default hard-coded Django SECRET_KEY with a unique, securely generated key to prevent exploitation. No vendor advisory or patch links were provided, so verify with official Kiwi TCMS sources for the latest remediation guidance.

Description

Kiwi TCMS versions before 17.1 contain a vulnerability due to a hard-coded cryptographic key. This allows remote attackers to forge signed data by exploiting the publicly known Django SECRET_KEY found in the source code. The flaw enables attackers to tamper with signed cookie-based messages and django.core.signing payloads, weakening protections for password-reset and session-authentication mechanisms if the default key is used.

References

Community reviews

Loading reviews…