CVE-2026-4105

MEDIUMNVD 6.76.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.7 under NVD CVSS v3. EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

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

6.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in systemd. The systemd-machined service contains an Improper Access Control vulnerability due to insufficient validation of the class parameter in the RegisterMachine D-Bus (Desktop Bus) method. A local unprivileged user can exploit this by attempting to register a machine with a specific class value, which may leave behind a usable, attacker-controlled machine object. This allows the attacker to invoke methods on the privileged object, leading to the execution of arbitrary commands with root privileges on the host system.

CVSS v3
6.7
EG Score
6.7MEDIUMmedium confidence
EG Risk
30
EG Risk 30/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)
Severity67% × 45%
Impact severity (EG Severity): CVSS 6.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability 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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
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 (6.7): severity, escalated by confirmed exploitation. This CVE's 6.7 is its impact severity (EG Severity), not escalated.

EG Severity
6.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.1% 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: 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).

A fix is available. 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.

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

March 13, 2026

Last Modified

September 1, 2026

Advisory Details (4)

Auto-updated Apr 30, 2026
Patch available. Sources: redhat, github.
GitHub advisoryMentions a patch (unverified)

Local privilege escalation in systemd-machined · Advisory · systemd/systemd · GitHub

https://github.com/systemd/systemd/security/advisories/GHSA-4h6x-r8vx-3862
Red HatMentions a patch (unverified)

2447262 – (CVE-2026-4105) CVE-2026-4105 systemd: systemd: Privilege escalation via improper access control in RegisterMachine D-Bus method

https://bugzilla.redhat.com/show_bug.cgi?id=2447262
Red HatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-4105
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:7299

Vendor Advisories for CVE-2026-4105(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatsystemd-main-260.1-2.1.hum12026-04-09redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
systemd247.3-6 ... 247.3-7+deb11u7 (9 versions)
  • every version up to 247.3-7+deb11u8: fixed in 247.3-7+deb11u8
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
systemd252.11-1 ... 252.6-1+loong64 (31 versions)
  • every version up to 252.39-1~deb12u2: fixed in 252.39-1~deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
systemd257.7-1, 257.8-1~deb13u1, 257.8-1~deb13u2, 257.9-1~deb13u1
  • every version up to 257.13-1~deb13u1: fixed in 257.13-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
systemd257.13-1~deb13u1 ... 260~rc2-1 (21 versions)
  • every version up to 260~rc3-1: fixed in 260~rc3-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 35× 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.

Showing the most recent 100 of 210 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 110 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-4105?
CVE-2026-4105 is a medium-severity vulnerability; its CVE record was published on March 13, 2026. A flaw was found in systemd. The systemd-machined service contains an Improper Access Control vulnerability due to insufficient validation of the class parameter in the RegisterMachine D-Bus (Desktop Bus) method. A local unprivileged user can exploit this by attempting to register a machine with a…
When was CVE-2026-4105 made public?
CVE-2026-4105 was made public on March 13, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on March 13, 2026. EchelonGraph's copy of the record carries a last-modified date of September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-4105 actively exploited?
CVE-2026-4105 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-4105?
CVE-2026-4105 has a CVSS v3 base score of 6.7 (NVD).
How do I remediate CVE-2026-4105?
A fix for CVE-2026-4105 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-4105 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-4105?

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

Book a Demo →Browse All CVEs