CVE-2026-44724

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 46% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

systeminformation is a System and OS information library for node.js. From 4.17.0 to 5.31.5, on Linux, systeminformation is vulnerable to command injection in networkInterfaces() when an active NetworkManager connection profile name contains shell metacharacters. The vulnerable value is obtained internally from real nmcli device status output. The library sanitizes the network interface name before using it in shell commands, but it does not apply equivalent sanitization to the parsed NetworkManager connection profile name. That unsanitized connectionName is then interpolated into three shell command strings executed through execSync(). This vulnerability is fixed in 5.31.6.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
51(Track*)
EG Risk 51/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
54%
KEV
Not listed

Published

May 27, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Jun 4, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Linux command injection in networkInterfaces() via unsanitized NetworkManager connection profile name · Advisory · sebhildebrandt/systeminformation · GitHub

https://github.com/sebhildebrandt/systeminformation/security/advisories/GHSA-hvx9-hwr7-wjj9

Vendor Advisories for CVE-2026-44724(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-mod-arch-mlflow-rhel9:17866122192026-08-27redhat
redhatrhdh/rhdh-hub-rhel9:17827612442026-06-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
jupyterlab4.0.11+ds1+~cs11.25.27-7 ... 4.4.8+ds1+~3.1.0+~0.16.6+~cs1.4.4-1 (27 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
jupyterlab4.0.11+ds1+~cs11.25.27-7 ... 4.0.11+ds4+~cs11.25.27-4 (10 versions)4.0.11+ds5+~cs11.25.27-1—
npm(1)
PackageVulnerable rangeFixed inDependents
systeminformation—5.31.6—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 187 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 07:34 UTCEG score recompute
  3. 2026-09-14 07:34 UTCVendor advisory
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-12 15:01 UTCEPSS rescore
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 09:37 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-28 16:46 UTCEG score recompute
  19. 2026-08-28 16:46 UTCVendor advisory
  20. 2026-08-28 15:59 UTCEG score recompute
  21. 2026-08-28 15:59 UTCVendor advisory
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-25 05:11 UTCEG score recompute
Show 75 more
  1. 2026-08-25 05:11 UTCVendor advisory
  2. 2026-08-23 14:54 UTCEG score recompute
  3. 2026-08-23 14:54 UTCVendor advisory
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 20:29 UTCVendor advisory
  7. 2026-08-21 01:24 UTCEG score recompute
  8. 2026-08-21 01:24 UTCVendor advisory
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 11:13 UTCEG score recompute
  11. 2026-08-20 11:13 UTCVendor advisory
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 09:12 UTCVendor advisory
  16. 2026-08-16 15:13 UTCEG score recompute
  17. 2026-08-16 15:13 UTCVendor advisory
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 02:46 UTCEG score recompute
  20. 2026-08-16 02:46 UTCVendor advisory
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-15 00:26 UTCVendor advisory
  24. 2026-08-14 12:55 UTCVendor advisory
  25. 2026-08-14 01:24 UTCEG score recompute
  26. 2026-08-14 01:24 UTCVendor advisory
  27. 2026-08-13 22:00 UTCEPSS rescore
  28. 2026-08-13 01:24 UTCVendor advisory
  29. 2026-08-12 13:52 UTCEG score recompute
  30. 2026-08-12 13:52 UTCVendor advisory
  31. 2026-08-12 13:51 UTCEPSS rescore
  32. 2026-08-12 01:06 UTCEG score recompute
  33. 2026-08-12 01:06 UTCVendor advisory
  34. 2026-08-11 13:32 UTCVendor advisory
  35. 2026-08-11 00:10 UTCEG score recompute
  36. 2026-08-11 00:10 UTCVendor advisory
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-10 06:08 UTCVendor advisory
  39. 2026-08-09 18:38 UTCEG score recompute
  40. 2026-08-09 18:38 UTCVendor advisory
  41. 2026-08-09 13:46 UTCEPSS rescore
  42. 2026-08-09 07:07 UTCVendor advisory
  43. 2026-08-08 19:36 UTCEG score recompute
  44. 2026-08-08 19:36 UTCVendor advisory
  45. 2026-08-08 16:37 UTCEPSS rescore
  46. 2026-08-08 06:25 UTCVendor advisory
  47. 2026-08-07 18:54 UTCEG score recompute
  48. 2026-08-07 18:54 UTCVendor advisory
  49. 2026-08-07 07:23 UTCVendor advisory
  50. 2026-08-06 19:52 UTCEG score recompute
  51. 2026-08-06 19:52 UTCVendor advisory
  52. 2026-08-06 13:46 UTCEPSS rescore
  53. 2026-08-06 08:21 UTCVendor advisory
  54. 2026-08-05 20:50 UTCEG score recompute
  55. 2026-08-05 20:50 UTCVendor advisory
  56. 2026-08-05 19:17 UTCEPSS rescore
  57. 2026-08-04 15:10 UTCEPSS rescore
  58. 2026-08-04 10:38 UTCEPSS rescore
  59. 2026-08-04 03:56 UTCVendor advisory
  60. 2026-08-03 16:25 UTCEG score recompute
  61. 2026-08-03 16:25 UTCVendor advisory
  62. 2026-08-03 10:36 UTCEPSS rescore
  63. 2026-08-03 01:38 UTCVendor advisory
  64. 2026-08-02 14:07 UTCVendor advisory
  65. 2026-08-02 02:36 UTCEG score recompute
  66. 2026-08-02 02:36 UTCVendor advisory
  67. 2026-08-02 02:27 UTCEPSS rescore
  68. 2026-08-01 15:05 UTCEG score recompute
  69. 2026-08-01 15:05 UTCVendor advisory
  70. 2026-08-01 04:16 UTCEPSS rescore
  71. 2026-07-31 07:07 UTCEG score recompute
  72. 2026-07-31 07:07 UTCVendor advisory
  73. 2026-07-30 16:28 UTCEPSS rescore
  74. 2026-07-30 01:30 UTCEPSS rescore
  75. 2026-07-29 14:45 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44724?
CVE-2026-44724 is a high vulnerability published on May 27, 2026. systeminformation is a System and OS information library for node.js. From 4.17.0 to 5.31.5, on Linux, systeminformation is vulnerable to command injection in networkInterfaces() when an active NetworkManager connection profile name contains shell metacharacters. The vulnerable value is obtained…
When was CVE-2026-44724 disclosed?
CVE-2026-44724 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44724 actively exploited?
CVE-2026-44724 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 46.0% of all scored CVEs.
What is the CVSS score of CVE-2026-44724?
CVE-2026-44724 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-44724?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44724, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44724

Explore →

Is Your Infrastructure Affected by CVE-2026-44724?

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

Start Free Scan →Browse All CVEs