dbcve.org
OpenmeetingsApplication · Apache

CVE-2026-33266

HIGH · 7.5 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to 9.0.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache OpenMeetings uses a hard-coded default encryption key for remember-me cookie functionality. When the default key is not changed by administrators, stolen cookies can be decrypted to obtain full user credentials, enabling account takeover.

MitigationUpgrade to version 9.0.0 and manually change the default encryption key in openmeetings.properties to a unique, strong value; ensure any existing remember-me tokens are invalidated after the key rotation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenmeetingsApplication
Affected:>= 6.1.0, < 9.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Apache OpenMeetings version
    Run command to retrieve installed version (e.g., rpm -q openmeetings, dpkg -l openmeetings, or check installation directory for version file)
    Affected if version is greater than or equal to 6.1.0 and less than 9.0.0
  2. Verify remember-me feature is enabled
    Inspect the openmeetings.properties configuration file for remember-me related settings (typically in /opt/openmeetings/conf/ or similar installation directory)
    Affected if remember-me cookie functionality is enabled in configuration
  3. Locate encryption key configuration
    Search openmeetings.properties for encryption key properties (look for keys related to cookie encryption, secretKey, or similar cryptographic configuration)
    Affected if encryption key property exists in configuration file
  4. Compare key against default value
    Read the configured encryption key value and determine if it matches the Apache OpenMeetings default hard-coded key (compare the full key string)
    Affected if the configured encryption key matches the default hard-coded value and has not been changed by administrator

Affected if OpenMeetings version is >= 6.1.0 and < 9.0.0, remember-me cookies are enabled, and the encryption key was not changed from the default value.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.0.0 or later
Fixed in 9.0.0
Interim mitigation

Upgrade to version 9.0.0 and manually change the default encryption key in openmeetings.properties to a unique, strong value; ensure any existing remember-me tokens are invalidated after the key rotation.

Recommended fix High confidence

9.0.0

  1. 1. Create a full backup of the current Apache OpenMeetings installation, database, and configuration files (especially openmeetings.properties).
  2. 2. Stop the Apache OpenMeetings service.
  3. 3. Download Apache OpenMeetings version 9.0.0 from the official Apache distribution repository (https://openmeetings.apache.org/download.html).
  4. 4. Install or extract version 9.0.0 following the official upgrade documentation.
  5. 5. Restore any custom configurations from the backup (verify openmeetings.properties does NOT contain hardcoded encryption keys).
  6. 6. Start the OpenMeetings service.
  7. 7. Verify the upgrade was successful by logging in and testing the remember-me functionality.
  8. 8. Confirm that the new installation generates a unique/rotated encryption key rather than using the default value.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openmeetings Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33266 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33266 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data