# CVE-2026-86241: liufee FeehiCMS hard-coded cryptographic key in cookie validation

Source: https://junglewise.ai/threats/cve-2026-86241-liufee-feehicms-hard-coded-cryptographic-key-in-cookie-validation  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-07. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-86241 · Severity: medium · CVSS 4.3 · Published 2026-09-07

FeehiCMS, a content management system, ships with an empty cryptographic key used to sign and validate HTTP cookies. This weakness allows attackers to forge session cookies and bypass authentication, potentially gaining unauthorized access to user accounts and sensitive data. The vulnerability affects all production and development deployments, including Docker-based installations.

## Quick answers

**Is CVE-2026-86241 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-86241 being exploited in the wild.

**How severe is CVE-2026-86241?** Medium severity, with a CVSS score of 4.3, published 7 September 2026.

**Which products and versions are affected?** liufee FeehiCMS up to 2.1.1.

**Is there a fix for CVE-2026-86241?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-86241 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-86241?** Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a use of a hard-coded (specifically, empty) cryptographic key in the Yii2 framework's cookie validation component. The vulnerable configuration exists in environments/prod/backend/config/main-local.php and equivalent frontend/dev environment files, where the cookieValidationKey parameter is left empty by default. Yii2 uses this key to sign cookies via HMAC-SHA256; an empty key means any cookie can be forged remotely without authentication. The Docker deployment entry point does not auto-generate a random key, ensuring all containerized instances are vulnerable by default. An attacker can forge arbitrary cookies to impersonate users and escalate privileges.

## Affected products

- liufee FeehiCMS up to 2.1.1

## Timeline

- 2026-07-22: disclosed: Issue opened on GitHub
- 2026-09-07: advisory: CVE-2026-86241 published

## References

- [https://github.com/liufee/cms/issues/96](https://github.com/liufee/cms/issues/96)
- [https://github.com/yang5ynag/cve/blob/main/FEHI-003-Empty-cookieValidationKey.md](https://github.com/yang5ynag/cve/blob/main/FEHI-003-Empty-cookieValidationKey.md)