CVE-2026-54161

HIGHPre-NVD 8.18.1
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (51st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-116198 (ENISA EUVD)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.1Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

Network UPS Tools is a collection of programs which provide a common interface for monitoring and administering UPS, PDU and SCD hardware. From 2.8.3 to 2.8.5, upsmon in clients/upsmon.c inserts the server-supplied ups.alarm value into shell commands executed by notify(), async_notify(), and wall(). When a monitored device reports an ALARM state and an operator has configured NOTIFYCMD with EXEC in NOTIFYFLAG ALARM, shell metacharacters in the alarm text are evaluated on POSIX or Windows and can execute arbitrary operating-system commands as the upsmon account, which is commonly root. An attacker can control the value through a malicious or compromised upsd, a man-in-the-middle on a plaintext upsd to upsmon connection, or a compromised UPS device whose driver supplies the alarm upstream of upsd; TLS between upsd and upsmon does not mitigate the compromised-device path. This vulnerability is fixed in 2.8.6.

CVSS v3
8.1
EG Score
8.1HIGHlow confidence
EG Risk
36
EG Risk 36/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
51st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 3, 2026

Last Modified

November 3, 2026

Advisory Details (5)

Auto-updated Nov 3, 2026
🔬 Proof of concept available. Fix named in the CVE record. Sources: github, github_commit, github_pr.
GitHub commit

commit ecf98e7542e4 (networkupstools/nut)

Fix landed in networkupstools/nut commit ecf98e7542e4 — awaiting tagged release

https://github.com/networkupstools/nut/commit/ecf98e7542e4ae2b62b211622ee26989274b2220
GitHub commit

commit dffba9115048 (networkupstools/nut)

Fix landed in networkupstools/nut commit dffba9115048 — awaiting tagged release

https://github.com/networkupstools/nut/commit/dffba911504866695be698bb5ec49eac40d0f66a
GitHub commit

commit 98e073d4cc31 (networkupstools/nut)

Fix landed in networkupstools/nut commit 98e073d4cc31 — awaiting tagged release

https://github.com/networkupstools/nut/commit/98e073d4cc31f9c73e2fa0c2677540487d902fe7
GitHub pull request

Handle `upsmon` NOTIFYCMD and `upssched` CMDSCRIPT values strictly as paths

Fix merged in networkupstools/nut PR #3499 on 2026-07-17 — awaiting tagged release

https://github.com/networkupstools/nut/pull/3499
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

upsmon: remote OS command injection (RCE) via attacker-controlled ups.alarm in NOTIFYCMD execution · Advisory · networkupstools/nut · GitHub

https://github.com/networkupstools/nut/security/advisories/GHSA-mjgp-j4gm-6qg5

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.6% · 51st percentile
  2. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  3. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  4. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  5. 2026-11-03 23:27 UTCEG score recompute
  6. 2026-11-03 22:46 UTCEG score recompute
  7. 2026-11-03 21:03 UTCENISA EUVD ID recordedEUVD-2026-116198 · Source: ENISA EUVD
  8. 2026-11-03 20:27 UTCEG score recompute
  9. 2026-11-03 20:01 UTCEG score recomputeFirst assessed: 8.1 HIGH
  10. 2026-11-03 20:01 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54161?
CVE-2026-54161 is a high-severity vulnerability; its CVE record was published on November 3, 2026. Network UPS Tools is a collection of programs which provide a common interface for monitoring and administering UPS, PDU and SCD hardware. From 2.8.3 to 2.8.5, upsmon in clients/upsmon.c inserts the server-supplied ups.alarm value into shell commands executed by notify(), async_notify(), and…
When was the CVE record for CVE-2026-54161 published?
The CVE record for CVE-2026-54161 was published on November 3, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2026; the record at its source may have been updated since.
Is CVE-2026-54161 actively exploited?
CVE-2026-54161 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54161?
CVE-2026-54161 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-54161?
The CVE record for CVE-2026-54161 names the fix: "This vulnerability is fixed in 2.8.6."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54161

Explore →

Is Your Infrastructure Affected by CVE-2026-54161?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs