Status: UPDATED | Advisory ID: CVE-2026-33266
| CVE | CVE-2026-33266 |
| CVSS Score / Version | 7.5 (High) / CVSS v3.1 |
| Updated | 2026-09-24 |
| CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CVSS Prose | attack vector is network; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is none; availability impact is none. |
| Affected products | Apache OpenMeetings |
| Classified as | CWE-321 (Use of Hard-coded Cryptographic Key) |
| Exploitation prediction (EPSS) | 0.34% probability of exploitation in the next 30 days (25% percentile) -- FIRST.org's EPSS model. |
| Vendor | Product | Affected Versions | Patch Status |
|---|---|---|---|
| Apache | OpenMeetings |
| Subsystems | General OT |
| Sectors | Multiple |
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.
Monitor Apache's web page for any future patch releases. See vendor advisory link below.
| Source | Reference |
|---|---|
| NVD | https://nvd.nist.gov/vuln/detail/CVE-2026-33266 |
| CVE | https://www.cve.org/CVERecord?id=CVE-2026-33266 |
| Vendor advisory | https://lists.apache.org/thread/b05jnp9563v49zq494lox9kjbhhf2w66 |