# CVE-2026-77914: rConfig Core 8.0.0 < 8.2.13 Core Path Traversal via Export Download Endpoint

> Authenticated attackers can read arbitrary files via path traversal in the export download endpoint of rConfig Core.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/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:** 24 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-6928-5hpx-7r3v, GHSA-m5rw-jcrm-mmwc

## What is CVE-2026-77914?

CVE-2026-77914 is a high-severity path traversal vulnerability in rconfig, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

rConfig Core 8.0.0 before 8.2.13 contains a path traversal vulnerability that allows authenticated users to read arbitrary files by supplying crafted filenames containing directory traversal sequences to the export download endpoint. Attackers can manipulate the filename parameter with traversal sequences to escape the intended export directory and access files outside it that are readable by the application process.

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

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


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

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

## Is CVE-2026-77914 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77914 is a high-severity path traversal vulnerability in rconfig, published on 24 Aug 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-77914 in the wild and no public exploit code.

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

## Sources

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

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