# CVE-2026-33005: Apache OpenMeetings: Insufficient checks in FileWebService

> Registered users can access metadata of any folder by ID due to insufficient privilege checks in the FileWebService.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-78cg-fc6c-w44w

## What is CVE-2026-33005?

CVE-2026-33005 is a medium-severity missing authorization vulnerability in Apache OpenMeetings, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Handling of Insufficient Privileges vulnerability in Apache OpenMeetings.

Any registered user can query web service with their credentials and get files/sub-folders of any folder by ID (metadata only NOT contents). Metadata includes id, type, name and some other field. Full list of fields get be checked at FileItemDTO object.

This issue affects Apache OpenMeetings: from 3.10 before 9.0.0.

Users are recommended to upgrade to version 9.0.0, which fixes the issue.

Weakness: CWE-274 (Improper Handling of Insufficient Privileges)

## Which versions are affected by CVE-2026-33005?

2 open source packages ship an affected version, including org.apache.openmeetings:openmeetings-parent. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.openmeetings:openmeetings-parent` | Maven | From 3.10 | 9.0.0 |
| `org.apache.openmeetings:openmeetings-parent` | Maven | From 3.10 | 9.0.0 |

Products: Apache Openmeetings.

## How do I fix CVE-2026-33005?

Upgrade org.apache.openmeetings:openmeetings-parent to 9.0.0 or later.

## Is CVE-2026-33005 being exploited?

There is no known exploitation of CVE-2026-33005 in the wild and no public exploit code.

## Other vulnerabilities in Apache OpenMeetings

- [CVE-2017-7664](https://insights.sbomify.com/CVE-2017-7664/): Apache OpenMeetings does not correctly validate uploaded XML documents (critical 10.0)
- [CVE-2024-54676](https://insights.sbomify.com/CVE-2024-54676/): Apache OpenMeetings: Deserialisation of untrusted data in cluster mode (critical 9.8)
- [CVE-2023-28326](https://insights.sbomify.com/CVE-2023-28326/): Apache OpenMeetings: allows user impersonation (critical 9.8)
- [CVE-2016-8736](https://insights.sbomify.com/CVE-2016-8736/): Apache OpenMeetings RCE (critical 9.8)
- [CVE-2017-7673](https://insights.sbomify.com/CVE-2017-7673/): Apache OpenMeetings has Inadequate Encryption Strength (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33005 and fix it if it is affected.

What it is: CVE-2026-33005 is a medium-severity missing authorization vulnerability in Apache OpenMeetings, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33005 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.openmeetings:openmeetings-parent (Maven): affected from 3.10; fixed in 9.0.0
- org.apache.openmeetings:openmeetings-parent (Maven): affected from 3.10; fixed in 9.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33005/ (Markdown: https://insights.sbomify.com/CVE-2026-33005/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33005
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33005
- OSV: https://osv.dev/vulnerability/CVE-2026-33005

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33005/
Summaries are generated and may contain mistakes; the official description above is the record.