Is CVE-2026-84190 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-84190 being exploited in the wild.

How severe is CVE-2026-84190?

High severity, with a CVSS score of 7.2, published 1 September 2026.

Which products and versions are affected?

Librenms before 26.5.0; librenms/librenms (Packagist) ECOSYSTEM:introduced=0,fixed=26.5.0.

Is there a fix for CVE-2026-84190?

Yes. librenms/librenms (Packagist): upgrade to 26.5.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-84190 attacked?

It is attacked over the network.

Am I affected by CVE-2026-84190?

Check whether you run Librenms or librenms/librenms (Packagist) 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.

CVE-2026-84190: LibreNMS AboutController remote code execution in snmpget configuration

CVE-2026-84190 · Severity: high · CVSS 7.2 · Published 2026-09-01

LibreNMS is an open-source network monitoring platform used by organizations to track and manage network devices and services. A vulnerability in the AboutController allows authenticated administrators to execute arbitrary code on the web server by modifying the snmpget configuration parameter to point to a malicious executable. Successful exploitation results in complete server compromise, enabling attackers to steal credentials, create backdoors, and disrupt monitoring operations.

Technologies: Librenms, librenms/librenms (Packagist). Vendors: Librenms, Packagist.

Quick answers

Is CVE-2026-84190 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-84190 being exploited in the wild.
How severe is CVE-2026-84190?: High severity, with a CVSS score of 7.2, published 1 September 2026.
Which products and versions are affected?: Librenms before 26.5.0; librenms/librenms (Packagist) ECOSYSTEM:introduced=0,fixed=26.5.0.
Is there a fix for CVE-2026-84190?: Yes. librenms/librenms (Packagist): upgrade to 26.5.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-84190 attacked?: It is attacked over the network.
Am I affected by CVE-2026-84190?: Check whether you run Librenms or librenms/librenms (Packagist) 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.

How to fix

librenms/librenms (Packagist): upgrade to 26.5.0 or later
```
composer require librenms/librenms:^26.5.0
```

Technical details

The vulnerability exists in LibreNMS's AboutController (app/Http/Controllers/AboutController.php line 85), where the snmpget configuration value is retrieved from the database and passed directly to shell_exec() without proper validation. While a sanitizePath() function attempts to block special characters (;, `, #, $, |, &, ', ", >, <, parentheses), it only prevents direct command injection and does NOT validate the destination of the executable path. An authenticated administrator can bypass this by modifying the snmpget configuration via the web interface (/settings/snmpget) to point to a pre-existing malicious executable on the system, then trigger execution by accessing the /about endpoint. The fix requires replacing shell_exec() with Symfony's Process component to properly separate command arguments from executable paths.

Affected products

LibreNMS LibreNMS before 26.5.0

Identifiers

CVE-2026-84190
GHSA-jf24-8g2h-2wg7

Timeline

2026-08-04: disclosed
2026-09-01: advisory
2026-09-01: patched: Version 26.5.0 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.