CVE-2026-78422

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% 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 week
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Subject::new_for_owner() in the zbus_polkit crate encodes the uid entry of a unix-process polkit subject as an unsigned 32-bit integer (D-Bus type u), whereas the org.freedesktop.PolicyKit1.Authority interface specifies a signed 32-bit integer (D-Bus type i). Because of this type mismatch, polkit silently discards the caller-supplied UID and instead determines the subject's owner itself by looking up the PID in /proc, a lookup that is inherently subject to a time-of-check/time-of-use race.

Consequently, an application that passes a UID obtained from a trustworthy source — for example SO_PEERCRED Unix socket peer credentials — in order to defend against PID reuse receives no protection, and the supplied UID has no effect on the authorization decision. A local unprivileged attacker who can cause an authorized process to terminate and then win the race to have their own process assigned the same PID can be authorized under the identity of the terminated process, bypassing the polkit authorization check and performing actions the attacker is not entitled to.

This issue affects zbus_polkit before 5.1.0.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
33(Track)
EG Risk 33/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
Severity73% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

August 31, 2026

Last Modified

September 1, 2026

Advisory Details (2)

Auto-updated Aug 31, 2026
Patch available. Sources: github_pr.
generic

Making sure you're not a bot!

https://bugzilla.suse.com/show_bug.cgi?id=1277659
github_pr Patch Available

Use the correct type for sending UID to polkit

Patch available: z-galaxy/zbus_polkit zbus_polkit-5.1.0 (PR #101 merged 2026-08-30)

https://github.com/z-galaxy/zbus_polkit/pull/101

Vendor Advisories for CVE-2026-78422(1)

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

Affected Packages

(2 across 2 ecosystems)
crates.io(1)
PackageVulnerable rangeFixed inDependents
zbus_polkit5.1.0
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rust-zbus-polkit5.0.0-15.1.0-1

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 67× 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-09-19 05:37 UTCGHSA enrichment
  2. 2026-09-18 18:41 UTCGHSA enrichment
  3. 2026-09-18 07:44 UTCGHSA enrichment
  4. 2026-09-17 20:47 UTCEG score recompute
  5. 2026-09-17 20:47 UTCGHSA enrichment
  6. 2026-09-17 08:26 UTCGHSA enrichment
  7. 2026-09-16 21:29 UTCEG score recompute
  8. 2026-09-16 21:29 UTCGHSA enrichment
  9. 2026-09-16 14:08 UTCEPSS rescore
  10. 2026-09-16 10:23 UTCEG score recompute
  11. 2026-09-16 10:23 UTCGHSA enrichment
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-15 23:26 UTCGHSA enrichment
  14. 2026-09-15 12:01 UTCEG score recompute
  15. 2026-09-15 12:01 UTCGHSA enrichment
  16. 2026-09-15 03:12 UTCEPSS rescore
  17. 2026-09-15 03:12 UTCEPSS rescore
  18. 2026-09-15 01:04 UTCGHSA enrichment
  19. 2026-09-14 14:08 UTCGHSA enrichment
  20. 2026-09-14 03:11 UTCEG score recompute
  21. 2026-09-14 03:11 UTCGHSA enrichment
  22. 2026-09-13 16:15 UTCGHSA enrichment
  23. 2026-09-13 05:18 UTCGHSA enrichment
  24. 2026-09-12 18:22 UTCEG score recompute
  25. 2026-09-12 18:22 UTCGHSA enrichment
Show 42 more
  1. 2026-09-12 07:26 UTCGHSA enrichment
  2. 2026-09-11 20:30 UTCEG score recompute
  3. 2026-09-11 20:30 UTCGHSA enrichment
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 09:33 UTCGHSA enrichment
  7. 2026-09-10 22:37 UTCGHSA enrichment
  8. 2026-09-10 11:40 UTCEG score recompute
  9. 2026-09-10 11:40 UTCGHSA enrichment
  10. 2026-09-09 23:44 UTCGHSA enrichment
  11. 2026-09-09 10:32 UTCGHSA enrichment
  12. 2026-09-08 23:29 UTCEG score recompute
  13. 2026-09-08 23:29 UTCGHSA enrichment
  14. 2026-09-08 22:01 UTCEPSS rescore
  15. 2026-09-08 07:53 UTCGHSA enrichment
  16. 2026-09-07 20:53 UTCGHSA enrichment
  17. 2026-09-07 09:57 UTCGHSA enrichment
  18. 2026-09-06 22:54 UTCGHSA enrichment
  19. 2026-09-06 11:58 UTCGHSA enrichment
  20. 2026-09-06 01:02 UTCEG score recompute
  21. 2026-09-06 01:02 UTCGHSA enrichment
  22. 2026-09-05 14:03 UTCGHSA enrichment
  23. 2026-09-05 03:04 UTCGHSA enrichment
  24. 2026-09-04 16:05 UTCEG score recompute
  25. 2026-09-04 16:04 UTCGHSA enrichment
  26. 2026-09-04 05:07 UTCEPSS rescore
  27. 2026-09-04 05:06 UTCGHSA enrichment
  28. 2026-09-03 18:06 UTCGHSA enrichment
  29. 2026-09-03 07:00 UTCGHSA enrichment
  30. 2026-09-02 20:03 UTCGHSA enrichment
  31. 2026-09-02 08:03 UTCGHSA enrichment
  32. 2026-09-01 21:02 UTCGHSA enrichment
  33. 2026-09-01 15:43 UTCEG score recompute
  34. 2026-09-01 15:43 UTCGHSA enrichment
  35. 2026-09-01 15:03 UTCEG score recompute
  36. 2026-09-01 15:03 UTCGHSA enrichment
  37. 2026-09-01 13:54 UTCEPSS rescore
  38. 2026-09-01 13:17 UTCGHSA enrichment
  39. 2026-09-01 02:21 UTCGHSA enrichment
  40. 2026-08-31 15:22 UTCEG score recompute
  41. 2026-08-31 14:25 UTCEG score recompute
  42. 2026-08-31 14:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-78422?
CVE-2026-78422 is a high vulnerability published on August 31, 2026. Subject::newforowner() in the zbus_polkit crate encodes the uid entry of a unix-process polkit subject as an unsigned 32-bit integer (D-Bus type u), whereas the org.freedesktop.PolicyKit1.Authority interface specifies a signed 32-bit integer (D-Bus type i). Because of this type mismatch, polkit…
When was CVE-2026-78422 disclosed?
CVE-2026-78422 was first published in the National Vulnerability Database on August 31, 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-78422 actively exploited?
CVE-2026-78422 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.5% of all scored CVEs.
What is the CVSS score of CVE-2026-78422?
CVE-2026-78422 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-78422?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-78422, 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-78422

Explore →

Is Your Infrastructure Affected by CVE-2026-78422?

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