Is CVE-2026-33266 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-33266 being exploited in the wild.

How severe is CVE-2026-33266?

High severity, with a CVSS score of 7.5, published 9 April 2026.

Which products and versions are affected?

Apache Software Foundation OpenMeetings 6.1.0 to 8.0.0 (before 9.0.0); org.apache.openmeetings:openmeetings-parent (Maven) >= 6.1.0, < 9.0.0, ECOSYSTEM:introduced=6.1.0,fixed=9.0.0.

Is there a fix for CVE-2026-33266?

Yes. org.apache.openmeetings:openmeetings-parent (Maven): upgrade to 9.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-33266 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-33266?

Check whether you run Apache Openmeetings, Apache Software Foundation OpenMeetings or org.apache.openmeetings:openmeetings-parent (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-33266: Apache OpenMeetings hard-coded cryptographic key in remember-me cookies

Q: Is there a fix for CVE-2026-33266?

Yes. org.apache.openmeetings:openmeetings-parent (Maven): upgrade to 9.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-33266 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-33266?

Check whether you run Apache Openmeetings, Apache Software Foundation OpenMeetings or org.apache.openmeetings:openmeetings-parent (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-33266 · Severity: high · CVSS 7.5 · Published 2026-04-09

Apache OpenMeetings, a web-based application for video conferencing and collaboration, uses a predictable, hard-coded security key to protect 'remember-me' login cookies. If an administrator has not manually changed this default key, an attacker who obtains a user's session cookie can decrypt it to recover the user's full login credentials. This could lead to unauthorized access to sensitive meetings, private communications, and corporate data.

Technologies: Apache Openmeetings, Apache Software Foundation OpenMeetings, org.apache.openmeetings:openmeetings-parent (Maven). Vendors: Apache, Apache Software Foundation, Maven.

Quick answers

Is CVE-2026-33266 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-33266 being exploited in the wild.
How severe is CVE-2026-33266?: High severity, with a CVSS score of 7.5, published 9 April 2026.
Which products and versions are affected?: Apache Software Foundation OpenMeetings 6.1.0 to 8.0.0 (before 9.0.0); org.apache.openmeetings:openmeetings-parent (Maven) >= 6.1.0, < 9.0.0, ECOSYSTEM:introduced=6.1.0,fixed=9.0.0.
Is there a fix for CVE-2026-33266?: Yes. org.apache.openmeetings:openmeetings-parent (Maven): upgrade to 9.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-33266 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-33266?: Check whether you run Apache Openmeetings, Apache Software Foundation OpenMeetings or org.apache.openmeetings:openmeetings-parent (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.apache.openmeetings:openmeetings-parent (Maven): upgrade to 9.0.0 or later

# set org.apache.openmeetings:openmeetings-parent to 9.0.0 in your pom.xml or build.gradle

Technical details

A Use of Hard-coded Cryptographic Key (CWE-321) vulnerability exists in Apache OpenMeetings versions 6.1.0 through 8.0.0. The encryption key and salt used for 'remember-me' cookies are set to static default values in the 'openmeetings.properties' file and are not automatically rotated. If an administrator fails to manually update these default values, the cryptographic protection of the cookies is effectively nullified. An attacker who obtains a 'remember-me' cookie (e.g., via network sniffing or local access) can use the known default keys to decrypt the cookie and extract the user's plaintext credentials. The issue is resolved in version 9.0.0.

Affected products

Apache OpenMeetings 6.1.0 to 8.0.0 (before 9.0.0)

Identifiers

CVE-2026-33266
GHSA-wqxq-w68r-wg85

Timeline

2026-04-09: disclosed
2026-04-09: advisory
2026-04-09: patched: Fixed in version 9.0.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.