CVE-2026-33266: Apache OpenMeetings: Hardcoded Remember-Me Cookie Encryption Key and Salt
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-33266?
CVE-2026-33266 is classified as a medium severity vulnerability due to the use of a hardcoded remember-me cookie encryption key.
How do I fix CVE-2026-33266?
To mitigate CVE-2026-33266, change the default remember-me cookie encryption key in the openmeetings.properties configuration file.
Which versions of Apache OpenMeetings are affected by CVE-2026-33266?
CVE-2026-33266 affects Apache OpenMeetings versions from 6.1.0 to 9.0.0.
What type of vulnerability is CVE-2026-33266?
CVE-2026-33266 is a Use of Hard-coded Cryptographic Key vulnerability that compromises cookie security.
Who is affected by CVE-2026-33266?
Administrators of Apache OpenMeetings who do not change the default hardcoded settings are at risk due to CVE-2026-33266.