Skip to main content
Menu
CVEs

CVE

Kiwi TCMS forged signed data via hard-coded django secret key

CVE-2026-129882EUVD-2026-126438GHSA-M5Q7-M9Q7-PWMP

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

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 17.1
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 17.1.

Published
Last modified
Reference
Last checked
23/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

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.

cve.now Index

23Pcve.now Index 23 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.3/10CVSS 6.3
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 17.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129882 (Kiwi TCMS before 17.1 Hard-coded Django SECRET_KEY in Default Settings), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129882 (entry last updated 2026-11-16):
Affected:
- Kiwi TCMS Kiwi TCMS: fixed in 17.1
Fixed versions: 17.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129882 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129882 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/kiwitcms/kiwitcms/security/advisories/GHSA-m9h5-c637-cpcg
- https://github.com/kiwitcms/kiwitcms/commit/ae58d71662284b0da5fb3d2228f77ac16842139a
- https://github.com/kiwitcms/kiwitcms/releases/tag/v17.1
- https://github.com/kiwitcms/kiwitcms/blob/v17.0/tcms/settings/common.py#L24-L25
- https://www.vulncheck.com/advisories/kiwi-tcms-before-17.1-hard-coded-django-secret-key-in-default-settings
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129882
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129882"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • Kiwi TCMS Kiwi TCMS

    fixed in 17.1

Evidence 7

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Patch
  2. Repository
  3. Repository
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129882

Is CVE-2026-129882 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-129882?

Kiwi TCMS: before 17.1.Source: cve.now feed data

How do I fix CVE-2026-129882?

Upgrade to a fixed version: 17.1.Source: cve.now feed data