CVE-2026-33266: CWE-321 Use of Hard-coded Cryptographic Key in Apache Software Foundation Apache OpenMeetings
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.
AI Analysis
Technical Summary
CVE-2026-33266 describes a hard-coded cryptographic key vulnerability in Apache OpenMeetings. The remember-me cookie encryption key is set to a default value in the configuration file (openmeetings.properties) and is not automatically rotated. This allows an attacker who steals a valid cookie from a logged-in user to decrypt it and obtain full user credentials if the default key remains unchanged. The vulnerability affects versions from 6.1.0 before 9.0.0. The Apache Software Foundation recommends upgrading to version 9.0.0 to remediate this issue.
Potential Impact
An attacker who steals a remember-me cookie from a logged-in user can decrypt it to obtain full user credentials if the default encryption key is still in use. This compromises user account confidentiality but does not affect integrity or availability. The vulnerability has a high severity rating (CVSS 7.5) due to the potential for credential compromise without requiring user interaction or privileges.
Mitigation Recommendations
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.
CVE-2026-33266: CWE-321 Use of Hard-coded Cryptographic Key in Apache Software Foundation Apache OpenMeetings
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-33266 describes a hard-coded cryptographic key vulnerability in Apache OpenMeetings. The remember-me cookie encryption key is set to a default value in the configuration file (openmeetings.properties) and is not automatically rotated. This allows an attacker who steals a valid cookie from a logged-in user to decrypt it and obtain full user credentials if the default key remains unchanged. The vulnerability affects versions from 6.1.0 before 9.0.0. The Apache Software Foundation recommends upgrading to version 9.0.0 to remediate this issue.
Potential Impact
An attacker who steals a remember-me cookie from a logged-in user can decrypt it to obtain full user credentials if the default encryption key is still in use. This compromises user account confidentiality but does not affect integrity or availability. The vulnerability has a high severity rating (CVSS 7.5) due to the potential for credential compromise without requiring user interaction or privileges.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-03-18T14:16:42.998Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d7ce5e1cc7ad14dae8f916
Added to database: 4/9/2026, 4:05:50 PM
Last enriched: 4/17/2026, 12:17:50 PM
Last updated: 5/25/2026, 12:20:58 PM
Views: 63
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.