Kiwi TCMS has an Open Redirect via unvalidated next parameter in account confirmation endpoint

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2026-54724: 0.35% estimated exploitation activity in the next 30 days; percentile 28.36 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary An open redirect vulnerability in the account confirmation endpoint allows an unauthenticated attacker to craft a URL hosted on a legitimate Kiwi TCMS instance that redirects victims to an arbitrary external domain. The attack surface is particularly relevant for phishing campaigns targeting Kiwi TCMS users, as the malicious link originates from a trusted organizational hostname. Impact This is an open redirect vulnerability (CWE-601). Any unauthenticated attacker can exploit it against any user of a Kiwi TCMS deployment. The primary risk is phishing. Because Kiwi TCMS is typically deployed as an internal tool for engineering and QA teams, a redirect from the organization's own hostname carries high implicit trust. An attacker can use this endpoint to: - Redirect victims to a credential-harvesting page styled to match the Kiwi TCMS or corporate SSO login. - Bypass email security filters and link-reputation checks that allowlist the organization's domain. - Distribute malware…

Published by the source

6 Jul 2026, 21:27 UTC

Last modified by the source

13 Jul 2026, 16:43 UTC

Source last checked

26 Oct 2026, 13:46 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-hmj5-jm8h-h9fh

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-hmj5-jm8h-h9fh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54724

Advisory: Kiwi TCMS has an Open Redirect via unvalidated next parameter in account confirmation endpoint
IDs: CVE-2026-54724, GHSA-hmj5-jm8h-h9fh
Record: https://patchnext.com/advisories/cve-2026-54724 (revision 2, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI kiwitcms: affected <= 12.4

## Suggested inspection (read-only)
- `python -m pip show kiwitcms`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on kiwitcms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-hmj5-jm8h-h9fh (OSV record GHSA-hmj5-jm8h-h9fh lists affected ranges: PyPI kiwitcms >=0 <=12.4)
- Verified: https://github.com/advisories/GHSA-hmj5-jm8h-h9fh (GitHub-reviewed advisory GHSA-hmj5-jm8h-h9fh lists affected ranges: PyPI kiwitcms >=0 <=12.4)

Commands are suggestions: review each one before running it.