CVE-2026-33266highCWE-321

CVE-2026-33266: high-severity vulnerability in Apache OpenMeetings

Apache OpenMeetings: Hardcoded Remember-Me Cookie Encryption Key and Salt

Published · Updated

Follow this CVE+ Monitor Apache OpenMeetings+ Monitor org.apache.openmeetings:openmeetings-parent

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

21Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 7.5epss 0.3%
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Affected products
Apache Software Foundation · Apache OpenMeetings
Related CVEs — Apache OpenMeetings

In the same product, most dangerous first.

CVE-2024-54676CRITICALApache OpenMeetings: Deserialisation of untrusted data in cluster modeEPSS 68.8%CVE-2016-8736—CVE-2016-8736EPSS 4.8%CVE-2017-7688—CVE-2017-7688EPSS 3.0%CVE-2017-7685—CVE-2017-7685EPSS 2.9%CVE-2021-27576—Apache OpenMeetings: bandwidth can be overloaded with public web serviceEPSS 2.8%CVE-2017-7684—CVE-2017-7684EPSS 2.8%