Quick answers
- Is CVE-2026-40084 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40084 being exploited in the wild.
- How severe is CVE-2026-40084?
- Medium severity, with a CVSS score of 6.5, published 25 June 2026.
- Which products and versions are affected?
- Cacti <= 1.2.30.
- Is there a fix for CVE-2026-40084?
- A patch was published on 2026-04-12: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-40084 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-40084?
- Check whether you run Cacti 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
A path traversal vulnerability exists in Cacti versions 1.2.30 and prior due to insufficient validation of the 'format_file' parameter in the reporting module. The exploit occurs in two stages: first, an attacker with report management permissions (Realm 22) performs a stored injection by saving a malicious path into the database via 'lib/html_reports.php'. Second, when the report is generated, 'lib/reports.php' concatenates this unvalidated string with a base directory and passes it to the 'file()' function. This allows a remote authenticated attacker to bypass directory restrictions and read sensitive files, such as 'config.php', which contains database credentials. The issue is resolved in version 1.2.31 by implementing 'basename()' validation on the input.
Affected products
- Cacti Cacti <= 1.2.30
Timeline
- 2026-04-12: patched: Fix committed to repository
- 2026-06-19: advisory: GitHub Security Advisory published
- 2026-06-25: disclosed: CVE published to NVD