# CVE-2026-92970: HUBzero CMS through 2.2.32 Path Traversal via File Upload

> Authenticated users can exploit path traversal in file uploads to write arbitrary files, potentially leading to code execution.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:** 17 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-6wrp-rq46-2frr

## What is CVE-2026-92970?

CVE-2026-92970 is a high-severity path traversal vulnerability in hubzero-cms, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HUBzero CMS through 2.2.32 contains a path traversal vulnerability in project file upload handlers that allows authenticated project members to write arbitrary files outside the project repository. Attackers can supply traversal sequences in upload parameters to write files to attacker-chosen paths with web server privileges, potentially enabling code execution.

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

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


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

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

## Is CVE-2026-92970 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92970 is a high-severity path traversal vulnerability in hubzero-cms, published on 17 Sep 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-92970 in the wild and no public exploit code.

Affected product: hubzero-cms. 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-92970/ (Markdown: https://insights.sbomify.com/CVE-2026-92970/index.md)
```

## Sources

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

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