CVE-2026-72693

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
7.8EG
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.8Exploit: None knownExposed: 0

A fix is available — apply it.

openvt -u is intended to identify the owner of the current VT and then execute login as that user from a privileged context. In the documented kbrequest/init usage, the ownership test in authenticate_user() relies on stat("/proc//fd/0"). stat() on /proc//fd/0 follows the symlink to the underlying TTY device node. As a result, buf.st_uid reflects the owner of the TTY node rather than the owner of the process holding the file descriptor. If the TTY owner returns to root or the getty owner after logout while an unprivileged process still has fd 0 attached to that TTY, the check can incorrectly treat that process as belonging to the privileged console owner. Once that check succeeds, the -u path executes a passwordless login as the selected user. In the documented kbrequest/init deployment using openvt -us, this can result in passwordless login -f root on the spawned VT. This report establishes that privilege escalation path for that documented deployment; it does not claim equivalent reachability for deployments that do not use openvt -u from a privileged kbrequest/init path.

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

Published

August 11, 2026

Last Modified

September 15, 2026

Advisory Details (2)

Auto-updated Aug 11, 2026
Patch available. Sources: redhat.
redhat

2462115 – (CVE-2026-72693) CVE-2026-72693 kbd: Local privilege escalation in openvt via incorrect process owner verification allowing passwordless root login

https://bugzilla.redhat.com/show_bug.cgi?id=2462115
redhat Patch Available

CVE-2026-72693 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-72693

Vendor Advisories for CVE-2026-72693(5)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhcos-4.22.9.8.202609081748-02026-09-15redhat
redhatrhcos-4.22.9.8.202608251819-02026-09-01redhat
redhatkbd-0:2.6.4-8.el10_22026-08-20redhat
redhatkbd-0:2.4.0-12.el9_82026-08-20redhat
redhatkbd-main-2.10.0-2.hum12026-07-16redhat

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 rangeFixed inDependents
kbd2.5.1-1 ... 2.9.0-1 (9 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
kbd2.7.1-2, 2.7.1-2+exp1, 2.9.0-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
kbd2.7.1-2, 2.7.1-2+exp1, 2.9.0-1——

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 38× in last 7d / 184× 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 240 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-72693?
CVE-2026-72693 is a high vulnerability published on August 11, 2026. openvt -u is intended to identify the owner of the current VT and then execute login as that user from a privileged context. In the documented kbrequest/init usage, the ownership test in authenticateuser() relies on stat("/proc/<pid>/fd/0"). stat() on /proc/<pid>/fd/0 follows the symlink to the…
When was CVE-2026-72693 disclosed?
CVE-2026-72693 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72693 actively exploited?
CVE-2026-72693 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 98.7% of all scored CVEs.
What is the CVSS score of CVE-2026-72693?
CVE-2026-72693 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72693?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72693, 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-72693

Explore →

Is Your Infrastructure Affected by CVE-2026-72693?

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

Start Free Scan →Browse All CVEs