CVE-2026-16742

MEDIUMPre-NVD 6.76.7
EchelonGraph scoreLOW confidence

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). 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
6.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • 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.7MEDIUMlow confidence
EG Risk
30
EG Risk 30/100CISA SSVC

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
Severity67% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 10, 2026

Last Modified

September 1, 2026

Advisory Details (1)

Auto-updated Aug 10, 2026
🔬 Proof of concept available. Patch available. Sources: github.
githubMentions a patch (unverified)🟡 PoC Available

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-06ubuntu

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 2× in last 7d / 30× 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.

  1. 2026-10-06 18:22 UTCVendor advisory
  2. 2026-10-05 07:48 UTCVendor advisory
  3. 2026-10-04 04:26 UTCVendor advisory
  4. 2026-10-02 09:19 UTCEG score recompute
  5. 2026-10-02 09:19 UTCVendor advisory
  6. 2026-09-30 22:36 UTCEG score recompute
  7. 2026-09-30 22:36 UTCVendor advisory
  8. 2026-09-28 12:49 UTCVendor advisory
  9. 2026-09-27 12:46 UTCVendor advisory
  10. 2026-09-25 04:01 UTCEG score recompute
  11. 2026-09-25 04:01 UTCVendor advisory
  12. 2026-09-24 00:15 UTCEG score recompute
  13. 2026-09-24 00:15 UTCVendor advisory
  14. 2026-09-23 00:40 UTCVendor advisory
  15. 2026-09-22 01:19 UTCVendor advisory
  16. 2026-09-21 01:57 UTCVendor advisory
  17. 2026-09-19 23:55 UTCVendor advisory
  18. 2026-09-19 00:34 UTCVendor advisory
  19. 2026-09-18 01:14 UTCVendor advisory
  20. 2026-09-17 01:53 UTCEG score recompute
  21. 2026-09-17 01:53 UTCVendor advisory
  22. 2026-09-16 14:07 UTCEPSS rescore
  23. 2026-09-16 02:31 UTCVendor advisory
  24. 2026-09-15 02:00 UTCVendor advisory
  25. 2026-09-14 02:39 UTCVendor advisory
Show 51 more
  1. 2026-09-13 03:18 UTCVendor advisory
  2. 2026-09-12 03:57 UTCEG score recompute
  3. 2026-09-12 03:57 UTCVendor advisory
  4. 2026-09-11 14:52 UTCEPSS rescore
  5. 2026-09-11 09:36 UTCEPSS rescore
  6. 2026-09-11 04:36 UTCVendor advisory
  7. 2026-09-10 05:15 UTCVendor advisory
  8. 2026-09-09 05:51 UTCVendor advisory
  9. 2026-09-07 17:17 UTCVendor advisory
  10. 2026-09-06 01:27 UTCVendor advisory
  11. 2026-09-05 01:57 UTCEG score recompute
  12. 2026-09-05 01:57 UTCVendor advisory
  13. 2026-09-04 01:58 UTCVendor advisory
  14. 2026-09-03 02:31 UTCVendor advisory
  15. 2026-09-01 21:04 UTCVendor advisory
  16. 2026-09-01 15:17 UTCVendor advisory
  17. 2026-08-31 09:57 UTCVendor advisory
  18. 2026-08-30 10:30 UTCVendor advisory
  19. 2026-08-29 11:09 UTCEG score recompute
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-28 11:40 UTCVendor advisory
  22. 2026-08-27 07:30 UTCVendor advisory
  23. 2026-08-26 06:12 UTCEG score recompute
  24. 2026-08-26 06:12 UTCVendor advisory
  25. 2026-08-25 13:48 UTCEPSS rescore
  26. 2026-08-25 06:49 UTCEG score recompute
  27. 2026-08-25 06:49 UTCVendor advisory
  28. 2026-08-24 07:28 UTCVendor advisory
  29. 2026-08-23 08:06 UTCVendor advisory
  30. 2026-08-22 08:45 UTCVendor advisory
  31. 2026-08-21 09:24 UTCVendor advisory
  32. 2026-08-20 10:03 UTCVendor advisory
  33. 2026-08-19 10:42 UTCEG score recompute
  34. 2026-08-19 10:42 UTCVendor advisory
  35. 2026-08-18 11:17 UTCVendor advisory
  36. 2026-08-17 11:56 UTCVendor advisory
  37. 2026-08-16 12:36 UTCVendor advisory
  38. 2026-08-15 13:15 UTCVendor advisory
  39. 2026-08-14 13:53 UTCVendor advisory
  40. 2026-08-13 14:32 UTCVendor advisory
  41. 2026-08-12 15:11 UTCVendor advisory
  42. 2026-08-11 15:49 UTCEG score recompute
  43. 2026-08-11 15:49 UTCVendor advisory
  44. 2026-08-11 13:42 UTCEPSS rescore
  45. 2026-08-10 16:29 UTCEG score recompute
  46. 2026-08-10 16:29 UTCVendor advisory
  47. 2026-08-10 16:10 UTCEG score recompute
  48. 2026-08-10 16:10 UTCVendor advisory
  49. 2026-08-10 14:29 UTCEG score recompute
  50. 2026-08-10 13:36 UTCEG score recompute
  51. 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 vulnerability 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 disclosed?
CVE-2026-16742 was first published on August 10, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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