GHSA-C9FV-CGMM-2WG7

Vulnerability from github – Published: 2026-08-18 17:59 – Updated: 2026-08-18 17:59
VLAI
Summary
LibreNMS Vulnerable to Remote Code Execution by Signal Alert Transportation module
Details

Summary

A vulnerability has been identified that allows an authenticated administrator to execute arbitrary code on the host server. By adding an alert transport entry, an attacker with administrative privileges can execute malicious commands.

Details

The vulnerability is caused by an unsafe exec call in deliverAlert function of LibreNMS/Alert/Transport/Signal.php. Escapes for the path of signal-cli and the Recipient field are insufficient to prevent command-line injection.

The composer_wrapper.php under scripts is also vulnerable to command injection (unsafe exec calls) by passing the injected command as an argument, and it is accepting arguments passed by deliverAlert.

By chaining these unsafe exec calls, malicious admin user can execute any executables in the server's filesystem.

PoC

  1. Under Dashboard -> Alert -> Alert Transports

image

  1. Create a new Alert Transport entry. a. Select Signal as Transport type. b. Put ../scripts/composer_wrapper.php into Path. c. Put the command to execute under Recipient with ; at the start and the end of string.

image

  1. . Click Save Transport, and after the popup closed, click Test Transport button under Action of the created Alert Transport entry.

image

  1. The command is executed. image

Impact

This vulnerability allows a malicious actor to achieve Remote Code Execution (RCE), potentially leading to complete system compromise, data exfiltration, or lateral movement within the network.

Remediation Advice

Escape user inputs, and avoid passing them directly into exec function. (scripts/composer_wrapper.php) Avoid setting executable paths directly in web interface. Instead, use a config value, and only allow setting executable paths by command line interface. (LibreNMS/Alert/Transport/Signal.php)

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "librenms/librenms"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "21.6.0"
            },
            {
              "fixed": "26.5.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-55182"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-77"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-08-18T17:59:56Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "### Summary\nA vulnerability has been identified that allows an authenticated administrator to execute arbitrary code on the host server. By adding an alert transport entry, an attacker with administrative privileges can execute malicious commands.\n\n### Details\nThe vulnerability is caused by an unsafe `exec` call in `deliverAlert` function of `LibreNMS/Alert/Transport/Signal.php`. Escapes for the path of `signal-cli` and the `Recipient` field are insufficient to prevent command-line injection. \n\nThe `composer_wrapper.php` under `scripts` is also vulnerable to command injection (unsafe `exec` calls) by passing the injected command as an argument, and it is accepting arguments passed by `deliverAlert`.\n\nBy chaining these unsafe `exec` calls, malicious admin user can execute any executables in the server\u0027s filesystem.\n\n### PoC\n\n1. Under Dashboard -\u003e Alert -\u003e Alert Transports\n\n\u003cimg width=\"282\" height=\"273\" alt=\"image\" src=\"https://github.com/user-attachments/assets/b72f55b0-b782-47d0-b4f7-75f498019345\" /\u003e\n\n2. Create a new Alert Transport entry.\n    a. Select `Signal` as `Transport type`.\n    b. Put `../scripts/composer_wrapper.php` into `Path`.\n    c. Put the command to execute under `Recipient` with `;` at the start and the end of string.\n\n\u003cimg width=\"767\" height=\"391\" alt=\"image\" src=\"https://github.com/user-attachments/assets/5e34bfa8-4bd5-40cb-9624-0d40e40ccdc5\" /\u003e\n\n3. . Click `Save Transport`, and after the popup closed, click `Test Transport` button under `Action` of the created Alert Transport entry.\n\n\u003cimg width=\"172\" height=\"90\" alt=\"image\" src=\"https://github.com/user-attachments/assets/7f83db07-fbf9-4be6-b247-533a6d7b9828\" /\u003e\n\n4. The command is executed.\n\u003cimg width=\"532\" height=\"216\" alt=\"image\" src=\"https://github.com/user-attachments/assets/d595b0fe-10cc-4050-b4b9-d290b658689d\" /\u003e\n\n### Impact\nThis vulnerability allows a malicious actor to achieve Remote Code Execution (RCE), potentially leading to complete system compromise, data exfiltration, or lateral movement within the network.\n\n### Remediation Advice\nEscape user inputs, and avoid passing them directly into `exec` function. (`scripts/composer_wrapper.php`)\nAvoid setting executable paths directly in web interface. Instead, use a config value, and only allow setting executable paths by command line interface. (`LibreNMS/Alert/Transport/Signal.php`)",
  "id": "GHSA-c9fv-cgmm-2wg7",
  "modified": "2026-08-18T17:59:56Z",
  "published": "2026-08-18T17:59:56Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/librenms/librenms/security/advisories/GHSA-c9fv-cgmm-2wg7"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/librenms/librenms"
    },
    {
      "type": "WEB",
      "url": "https://github.com/librenms/librenms/releases/tag/26.5.0"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "LibreNMS Vulnerable to Remote Code Execution by Signal Alert Transportation module"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…