Use of Hard-coded Cryptographic Key vulnerability in Apache OpenMeetings.

The remember-me cookie encryption key is set to default value in openmeetings.properties and not being auto-rotated. In case OM admin hasn't changed the default encryption key, an attacker who has stolen a cookie from a logged-in user can get full user credentials.


This issue affects Apache OpenMeetings: from 6.1.0 before 9.0.0.

Users are recommended to upgrade to version 9.0.0, which fixes the issue.

Project Subscriptions

No data.

Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Thu, 09 Apr 2026 17:30:00 +0000

Type Values Removed Values Added
References

Thu, 09 Apr 2026 16:00:00 +0000

Type Values Removed Values Added
Description Use of Hard-coded Cryptographic Key vulnerability in Apache OpenMeetings. The remember-me cookie encryption key is set to default value in openmeetings.properties and not being auto-rotated. In case OM admin hasn't changed the default encryption key, an attacker who has stolen a cookie from a logged-in user can get full user credentials. This issue affects Apache OpenMeetings: from 6.1.0 before 9.0.0. Users are recommended to upgrade to version 9.0.0, which fixes the issue.
Title Apache OpenMeetings: Hardcoded Remember-Me Cookie Encryption Key and Salt
Weaknesses CWE-321
References

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-04-09T16:29:21.634Z

Reserved: 2026-03-18T14:16:42.998Z

Link: CVE-2026-33266

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-04-09T16:16:26.960

Modified: 2026-04-09T17:16:24.960

Link: CVE-2026-33266

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses