# CVE-2026-49488: Apache OpenMeetings: Arbitrary File Read

> A moderator can read arbitrary files on the server via path traversal, exposing sensitive data like credentials.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** No
- **Published:** 14 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-436m-m73c-vq4g

## What is CVE-2026-49488?

CVE-2026-49488 is a medium-severity path traversal vulnerability in Apache OpenMeetings, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache OpenMeetings.

This issue affects Apache OpenMeetings: from 5.0.0 before 9.1.0.
An attacker with moderator rights in any room can read arbitrary files accessible to the OS account running the OM server, including credentials and secrets, via a crafted download request.

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

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Apache Openmeetings.

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

No fix has been published for CVE-2026-49488 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-49488 being exploited?

There is no known exploitation of CVE-2026-49488 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-49488 and fix it if it is affected.

What it is: CVE-2026-49488 is a medium-severity path traversal vulnerability in Apache OpenMeetings, published on 14 Jul 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-49488 in the wild and no public exploit code.

Affected product: Apache OpenMeetings. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-49488/ (Markdown: https://insights.sbomify.com/CVE-2026-49488/index.md)
```

## Sources

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

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