Use of Hard-coded Cryptographic Key vulnerability in Apache OpenMeetings.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

1. Apr 9, 2026 · NIST NVD

   Detected

   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.

2. Jun 17, 2026 · NIST NVD

   Updated

   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.

Affected

• cpe apache/openmeetingsversion unspecified

Sources

• CVE.orgVulnerability recordCVE-2026-33266

  Official CVE identifier

  cve.org
• NIST NVDVulnerability recordCVE-2026-33266

  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

  nvd.nist.gov

References

• Mailing List · openwall.com
• Mailing List · lists.apache.org