CVE-2026-33266: Apache OpenMeetings · Use of Hard-coded Cryptographic Key
Affects Apache OpenMeetingsSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 9.0.0 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.0.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Apache OpenMeetings to 9.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache OpenMeetings | Affected
| Fixed in
|
Mavenorg.apache.openmeetings/openmeetingspkg:maven/org.apache.openmeetings/openmeetingsOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade Apache OpenMeetings to version 9.0.0, which fixes this vulnerability by removing the hard-coded default encryption key and implementing proper key management. Until upgraded, administrators should ensure the default remember-me cookie encryption key in openmeetings.properties is changed to a unique, strong value. Patch status is not explicitly confirmed in the advisory, but upgrading to version 9.0.0 is the recommended remediation.
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.