CVE-2026-16742

MEDIUMPre-NVD 6.76.7
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: <0.1% (below the 1st 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: EPSS, a secondary CVSS source

Also known asEUVD-2026-55626 (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.

systemd-homed contains a local privilege escalation bug via arbitrary system group addition to a local, logged in, homed-managed user

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.
Exploitation<0.1% × 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
below the 1st
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.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
<0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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).

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.

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

August 10, 2026

Last Modified

October 23, 2026

Advisory Details (1)

Auto-updated Aug 10, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

systemd-homed: local privilege escalation via missing home-record signature verification on the authenticate path · Advisory · systemd/systemd · GitHub

https://github.com/systemd/systemd/security/advisories/GHSA-jm29-p7hh-vjhv

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuudev (259.5-0ubuntu3.4) @ resolute2026-10-23ubuntu

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:12(1)
PackageVulnerable rangeFix by version rangeDependents
systemd252.11-1 ... 262~rc3-1 (188 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
systemd257.13-1~deb13u1 ... 262~rc3-1 (40 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
systemd257.13-1~deb13u1 ... 261~rc4-1 (34 versions)
  • every version up to 261.2-1: fixed in 261.2-1
—

Weakness Classification(2)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 0× in last 7d / 13× 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-10-25 14:46 UTCEG score recompute
  2. 2026-10-23 20:32 UTCEG score recompute
  3. 2026-10-23 20:32 UTCVendor advisory
  4. 2026-10-23 06:19 UTCEG score recompute
  5. 2026-10-23 06:19 UTCVendor advisory
  6. 2026-10-18 04:00 UTCEG score recompute
  7. 2026-10-12 16:30 UTCEG score recompute
  8. 2026-10-11 20:09 UTCEG score recompute
  9. 2026-10-11 17:21 UTCEG score recompute
  10. 2026-10-11 14:54 UTCEG score recompute
  11. 2026-10-06 18:22 UTCVendor advisory
  12. 2026-10-05 07:48 UTCVendor advisory
  13. 2026-10-04 04:26 UTCVendor advisory
  14. 2026-10-02 09:19 UTCEG score recompute
  15. 2026-10-02 09:19 UTCVendor advisory
  16. 2026-09-30 22:36 UTCEG score recompute
  17. 2026-09-30 22:36 UTCVendor advisory
  18. 2026-09-28 12:49 UTCVendor advisory
  19. 2026-09-27 12:46 UTCVendor advisory
  20. 2026-09-25 04:01 UTCEG score recompute
  21. 2026-09-25 04:01 UTCVendor advisory
  22. 2026-09-24 00:15 UTCEG score recompute
  23. 2026-09-24 00:15 UTCVendor advisory
  24. 2026-09-23 00:40 UTCVendor advisory
  25. 2026-09-22 01:19 UTCVendor advisory
Show 61 more
  1. 2026-09-21 01:57 UTCVendor advisory
  2. 2026-09-19 23:55 UTCVendor advisory
  3. 2026-09-19 00:34 UTCVendor advisory
  4. 2026-09-18 01:14 UTCVendor advisory
  5. 2026-09-17 01:53 UTCEG score recompute
  6. 2026-09-17 01:53 UTCVendor advisory
  7. 2026-09-16 14:07 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  8. 2026-09-16 02:31 UTCVendor advisory
  9. 2026-09-15 02:00 UTCVendor advisory
  10. 2026-09-14 02:39 UTCVendor advisory
  11. 2026-09-13 03:18 UTCVendor advisory
  12. 2026-09-12 03:57 UTCEG score recompute
  13. 2026-09-12 03:57 UTCVendor advisory
  14. 2026-09-11 14:52 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  15. 2026-09-11 09:36 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  16. 2026-09-11 04:36 UTCVendor advisory
  17. 2026-09-10 05:15 UTCVendor advisory
  18. 2026-09-09 05:51 UTCVendor advisory
  19. 2026-09-07 17:17 UTCVendor advisory
  20. 2026-09-06 01:27 UTCVendor advisory
  21. 2026-09-05 01:57 UTCEG score recompute
  22. 2026-09-05 01:57 UTCVendor advisory
  23. 2026-09-04 01:58 UTCVendor advisory
  24. 2026-09-03 02:31 UTCVendor advisory
  25. 2026-09-01 21:04 UTCVendor advisory
  26. 2026-09-01 15:17 UTCVendor advisory
  27. 2026-08-31 09:57 UTCVendor advisory
  28. 2026-08-30 10:30 UTCVendor advisory
  29. 2026-08-29 11:09 UTCEG score recompute
  30. 2026-08-28 21:41 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  31. 2026-08-28 11:40 UTCVendor advisory
  32. 2026-08-27 07:30 UTCVendor advisory
  33. 2026-08-26 06:12 UTCEG score recompute
  34. 2026-08-26 06:12 UTCVendor advisory
  35. 2026-08-25 13:48 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  36. 2026-08-25 06:49 UTCEG score recompute
  37. 2026-08-25 06:49 UTCVendor advisory
  38. 2026-08-24 07:28 UTCVendor advisory
  39. 2026-08-23 08:06 UTCVendor advisory
  40. 2026-08-22 08:45 UTCVendor advisory
  41. 2026-08-21 09:24 UTCVendor advisory
  42. 2026-08-20 10:03 UTCVendor advisory
  43. 2026-08-19 10:42 UTCEG score recompute
  44. 2026-08-19 10:42 UTCVendor advisory
  45. 2026-08-18 11:17 UTCVendor advisory
  46. 2026-08-17 11:56 UTCVendor advisory
  47. 2026-08-16 12:36 UTCVendor advisory
  48. 2026-08-15 13:15 UTCVendor advisory
  49. 2026-08-14 13:53 UTCVendor advisory
  50. 2026-08-13 14:32 UTCVendor advisory
  51. 2026-08-12 15:11 UTCVendor advisory
  52. 2026-08-11 15:49 UTCEG score recompute
  53. 2026-08-11 15:49 UTCVendor advisory
  54. 2026-08-11 13:42 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  55. 2026-08-10 16:29 UTCEG score recompute
  56. 2026-08-10 16:29 UTCVendor advisory
  57. 2026-08-10 16:10 UTCEG score recompute
  58. 2026-08-10 16:10 UTCVendor advisory
  59. 2026-08-10 14:29 UTCEG score recompute
  60. 2026-08-10 13:36 UTCEG score recomputeFirst assessed: 6.7 MEDIUM
  61. 2026-08-10 13:36 UTCMITRE cvelistV5first tracked

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

Same vendor

2 shown

ubuntu:USN-8626-1

Frequently asked(5)

What is CVE-2026-16742?
CVE-2026-16742 is a medium-severity vulnerability; its CVE record was published on August 10, 2026. systemd-homed contains a local privilege escalation bug via arbitrary system group addition to a local, logged in, homed-managed user
When was CVE-2026-16742 made public?
CVE-2026-16742 was made public on August 10, 2026: that is the date its CVE record's CNA, The systemd project, gives for when the vulnerability was made public. The CVE record itself was published on August 10, 2026. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-16742 actively exploited?
CVE-2026-16742 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16742?
CVE-2026-16742 has a CVSS base score of 6.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16742?
A fix for CVE-2026-16742 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-16742?

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

Book a Demo →Browse All CVEs