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 — 4 sources updated 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.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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
Severity78% × 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
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 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(7)

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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
kbd2.5.1-1 ... 2.9.0-1 (9 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
kbd2.7.1-2, 2.7.1-2+exp1, 2.9.0-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
kbd2.7.1-2, 2.7.1-2+exp1, 2.9.0-1
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 138× 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 304 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 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.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-72693?
CVE-2026-72693 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-72693?
A fix for CVE-2026-72693 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72693 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-72693

Explore →

Is Your Infrastructure Affected by CVE-2026-72693?

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

Book a Demo →Browse All CVEs