How severe is CVE-2026-33266?

CVE-2026-33266 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-33266 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (14th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-33266?

CVE-2026-33266 affects Apache Openmeetings. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-33266?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-33266 have an EU (EUVD) identifier?

Yes. CVE-2026-33266 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-20936.

When was CVE-2026-33266 published?

CVE-2026-33266 was published on 2026-04-09 and last updated on 2026-06-17.

CVE-2026-33266

CVE-2026-33266 is a high-severity vulnerability in Apache Openmeetings with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-321.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (14th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-20936
Weakness: CWE-321
Affected product: Apache Openmeetings
Published: 2026-04-09
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-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 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.
How severe is CVE-2026-33266?: CVE-2026-33266 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-33266 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (14th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-33266?: CVE-2026-33266 affects Apache Openmeetings. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-33266?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-33266 have an EU (EUVD) identifier?: Yes. CVE-2026-33266 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-20936.
When was CVE-2026-33266 published?: CVE-2026-33266 was published on 2026-04-09 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:apache:openmeetings:*:*:*:*:*:*:*:*

More vulnerabilities in Apache Openmeetings

CVE-2017-7664 — Critical (CVSS 10.0): Uploaded XML documents were not correctly validated in Apache OpenMeetings 3.1.0.
CVE-2024-54676 — Critical (CVSS 9.8): Vendor: The Apache Software Foundation Versions Affected: Apache OpenMeetings from 2.1.0 before 8.0.0 Description:…
CVE-2023-28326 — Critical (CVSS 9.8): Vendor: The Apache Software Foundation Versions Affected: Apache OpenMeetings from 2.0.0 before 7.0.0 Description:…
CVE-2016-8736 — Critical (CVSS 9.8): Apache OpenMeetings before 3.1.2 is vulnerable to Remote Code Execution via RMI deserialization attack.
CVE-2017-7673 — Critical (CVSS 9.8): Apache OpenMeetings 1.0.0 uses not very strong cryptographic storage, captcha is not used in registration and forget…
CVE-2017-7681 — High (CVSS 8.8): Apache OpenMeetings 1.0.0 is vulnerable to SQL injection. This allows authenticated users to modify the structure of…

All CVEs affecting Apache Openmeetings →

Other CWE-321 vulnerabilities

CVE-2024-30207 — Critical (CVSS 10.0): A vulnerability has been identified in SIMATIC RTLS Locating Manager (6GT2780-0DA00) (All versions < V3.0.1.1), SIMATIC…
CVE-2014-5419 — Critical (CVSS 10.0): GE Multilink ML800, ML1200, ML1600, and ML2400 switches with firmware 4.2.1 and earlier and Multilink ML810, ML3000,…
CVE-2024-35344 — Critical (CVSS 9.9): Certain Anpviz products contain a hardcoded cryptographic key stored in the firmware of the device. This affects…
CVE-2026-28742 — Critical (CVSS 9.8): Naxclow devices use a uniform request-signing scheme based on a hard-coded, platform-wide salt embedded in every…
CVE-2026-32644 — Critical (CVSS 9.8): Specific firmware versions of Milesight AIOT cameras use SSL certificates with default private keys.
CVE-2025-67112 — Critical (CVSS 9.8): Use of a hard-coded AES-256-CBC key in the configuration backup/restore implementation of Small Cell Sercomm SCE4255W…

Browse all CWE-321 vulnerabilities →