cve.bz

CVE-2026-33266 apache openmeetings: Use of Hard-coded Cryptographic Key

7.5 highEPSS 0.3%Fix available

High (7.5) in apache openmeetings. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.openmeetings:openmeetings-parent 9.0.0.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-04-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-321 Use of Hard-coded Cryptographic Key
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-33266 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-33266?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-33266?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-33266 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-33266

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-33266](https://cve.bz/cve/badge/CVE-2026-33266.svg)](https://cve.bz/cve/CVE-2026-33266)

HTML:

<a href="https://cve.bz/cve/CVE-2026-33266"><img src="https://cve.bz/cve/badge/CVE-2026-33266.svg" alt="CVE-2026-33266"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache OpenMeetingsfrom 6.1.0 before 9.0.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-wqxq-w68r-wg85Mavenorg.apache.openmeetings:openmeetings-parent>=6.1.0 <9.0.09.0.0

References

Check your stackJSON