# CVE-2026-64826: rConfig path traversal in file download

Source: https://junglewise.ai/threats/cve-2026-64826-rconfig-path-traversal-in-file-download  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-12. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-64826 · Severity: medium · CVSS 6.5 · Published 2026-08-12

rConfig is a configuration management tool that allows network administrators to backup and export device configurations. A flaw in its export download feature allows authenticated users to read any file accessible by the web server, including sensitive application files containing encryption keys and database credentials. An attacker could exploit this to gain access to system secrets and compromise the entire infrastructure managed by rConfig.

Vendors: [Rconfig](https://junglewise.ai/threats/vendors/rconfig).

## Quick answers

**Is CVE-2026-64826 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-64826 being exploited in the wild.

**How severe is CVE-2026-64826?** Medium severity, with a CVSS score of 6.5, published 12 August 2026.

**Which products and versions are affected?** Rconfig before 8.2.13.

**Is there a fix for CVE-2026-64826?** A patch was published on 2026-08-10: Fix merged in commit d133a466a2df9d065177de9a8ed50f1bfe438aee Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-64826 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-64826?** Check whether you run Rconfig at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a path traversal flaw in the download_export() method of rConfig. The download endpoint concatenates a user-supplied filename parameter directly onto the export directory path without sanitization, allowing attackers to use ../ sequences to escape the base directory and access arbitrary files readable by the web server process. Authentication is required, but the attacker can traverse to sensitive files such as .env files containing database credentials and encryption keys. The fix, applied in version 8.2.13, uses basename() to extract only the filename portion and realpath() to verify the resolved file is actually within the export directory before serving it.

## Affected products

- rConfig rConfig before 8.2.13

## Timeline

- 2026-08-10: patched: Fix merged in commit d133a466a2df9d065177de9a8ed50f1bfe438aee
- 2026-08-12: disclosed

## References

- [https://github.com/rconfig/rconfig/commit/d133a466a2df9d065177de9a8ed50f1bfe438aee](https://github.com/rconfig/rconfig/commit/d133a466a2df9d065177de9a8ed50f1bfe438aee)
- [https://github.com/rconfig/rconfig/pull/349](https://github.com/rconfig/rconfig/pull/349)

## Related threats

- [rConfig OS Command Injection Vulnerability](https://junglewise.ai/threats/cve-2020-10221-rconfig-os-command-injection-vulnerability)