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.
Metrics
Affected Vendors & Products
References
History
Fri, 10 Apr 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Fri, 10 Apr 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache openmeetings |
|
| Vendors & Products |
Apache
Apache openmeetings |
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 |
|
Status: PUBLISHED
Assigner: apache
Published: 2026-04-09T15:52:36.105Z
Updated: 2026-04-10T18:49:13.351Z
Reserved: 2026-03-18T14:16:42.998Z
Link: CVE-2026-33266
Updated: 2026-04-09T16:29:21.634Z
Status : Awaiting Analysis
Published: 2026-04-09T16:16:26.960
Modified: 2026-04-13T15:02:47.353
Link: CVE-2026-33266
No data.