Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55182

Command Injection in librenms/librenms (CVE-2026-55182)

Summary

Command injection in librenms/librenms (CVE-2026-55182). Risk of unauthorized operations or information disclosure. Exploitable via exec. Mitigation: upgrade to 26.5.0 or later.

Original description

The description as published by the source.

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

  2. 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.

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

  4. The command is executed.

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.…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-55182 has been found in librenms/librenms.
Attackers can target a specific entry point like exec over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade librenms/librenms to 26.5.0 or later.
If unsure, ask your IT team or search "librenms/librenms CVE-2026-55182" on the vendor's site.

CVE-2026-55182 (librenms/librenms) — CWE-77
Attack surface: exec / deliverAlert / Recipient / composer_wrapper.php
Patched: 26.5.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-77) exists in librenms/librenms. Attackers reach the vulnerable code path via exec.

📍 Affected scope

Check the vendor advisory for the affected versions of librenms/librenms. Attack surface: exec / deliverAlert / Recipient / composer_wrapper.php.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 26.5.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'librenms/librenms' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'librenms/librenms' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で librenms/librenms を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade librenms/librenms to 26.5.0

    ステージング環境で 26.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer librenms/librenms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"26.5.0"}]}]
Packagist librenms/librenms
[{"type":"ECOSYSTEM","events":[{"introduced":"21.6.0"},{"fixed":"26.5.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details