CVE-2026-112314

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this weekElevated

Also known asEUVD-2026-120238 (ENISA EUVD) · GHSA-vhj5-cwj8-wqq6 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

clnttcp_call() in lib/rpc/clnt_tcp.c in MIT Kerberos 5 (aka krb5) does not free the RPC reply verifier between retries, which allows remote attackers to cause a denial of service (memory leak in GSS-RPC client programs) by injecting RPC replies with mismatched XIDs or by triggering authentication retries.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
65
EG Risk 65/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
60th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

November 9, 2026

Last Modified

November 13, 2026

Advisory Details (2)

Auto-updated Nov 9, 2026
Patch available. Sources: redhat.
Red Hat

2478446 – (CVE-2026-112314) CVE-2026-112314 krb5: MIT krb5 GSS-RPC client memory leak on XID mismatch retries

https://bugzilla.redhat.com/show_bug.cgi?id=2478446
Red HatMentions a patch (unverified)

CVE-2026-112314 - 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-112314

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkrb5-0:1.21.3-10.el10_2.22026-11-12redhat
redhatkrb5-0:1.21.3-11.el10_3.22026-11-12redhat
redhatkrb5-0:1.21.1-10.el9_8.32026-11-12redhat
redhatkrb5-0:1.21.1-10.el9_9.22026-11-12redhat

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

(5 across 5 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
krb5—
  • every version up to 1.22.3-r0: fixed in 1.22.3-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
krb5—
  • every version up to 1.22.3-r0: fixed in 1.22.3-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
krb51.20.1-2 ... 1.22.1-3 (23 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
krb51.21.3-5 ... 1.22.1-3 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
krb51.21.3-5, 1.22.1-1, 1.22.1-2, 1.22.1-2.1, 1.22.1-3
  • every version on: no fix on record
—

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 15× in last 7d / 15× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 02:28 UTCEchelonGraph re-scored
  2. 2026-11-13 02:28 UTCVendor advisory
  3. 2026-11-13 02:28 UTCGHSA enrichmentGHSA-vhj5-cwj8-wqq6 · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-11-13 00:37 UTCEchelonGraph re-scored
  5. 2026-11-13 00:37 UTCVendor advisory
  6. 2026-11-13 00:37 UTCGHSA enrichmentGHSA-vhj5-cwj8-wqq6 · GitHub severity HIGH · GitHub CVSS 7.5
  7. 2026-11-12 18:28 UTCEchelonGraph re-scored
  8. 2026-11-12 18:28 UTCGHSA enrichmentGHSA-vhj5-cwj8-wqq6 · GitHub severity HIGH · GitHub CVSS 7.5
  9. 2026-11-12 17:32 UTCEchelonGraph re-scored
  10. 2026-11-12 17:32 UTCGHSA enrichmentGHSA-vhj5-cwj8-wqq6 · GitHub severity HIGH · GitHub CVSS 7.5
  11. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  12. 2026-11-12 13:28 UTCEchelonGraph re-scored
  13. 2026-11-12 13:28 UTCGHSA enrichmentGHSA-vhj5-cwj8-wqq6 · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-11-12 13:02 UTCEchelonGraph re-scored
  15. 2026-11-12 13:02 UTCGHSA enrichmentGHSA-vhj5-cwj8-wqq6 · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  17. 2026-11-11 02:41 UTCEchelonGraph re-scored
  18. 2026-11-11 02:41 UTCGHSA enrichmentGHSA-vhj5-cwj8-wqq6 · GitHub severity HIGH · GitHub CVSS 7.5
  19. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  20. 2026-11-09 21:46 UTCEchelonGraph re-scored
  21. 2026-11-09 21:46 UTCGHSA enrichmentGHSA-vhj5-cwj8-wqq6 · GitHub severity HIGH · GitHub CVSS 7.5
  22. 2026-11-09 20:27 UTCEchelonGraph re-scored
  23. 2026-11-09 20:00 UTCENISA EUVD ID recordedEUVD-2026-120238 · Source: ENISA EUVD
  24. 2026-11-09 19:17 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  25. 2026-11-09 19:14 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-112314?
CVE-2026-112314 is a high-severity vulnerability; its CVE record was published on November 9, 2026. clnttcp_call() in lib/rpc/clnt_tcp.c in MIT Kerberos 5 (aka krb5) does not free the RPC reply verifier between retries, which allows remote attackers to cause a denial of service (memory leak in GSS-RPC client programs) by injecting RPC replies with mismatched XIDs or by triggering authentication…
When was CVE-2026-112314 made public?
CVE-2026-112314 was made public on November 9, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on November 9, 2026. EchelonGraph's copy of the record carries a last-modified date of November 13, 2026; the record at its source may have been updated since.
Is CVE-2026-112314 actively exploited?
CVE-2026-112314 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (60th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-112314?
CVE-2026-112314 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-112314?
A fix for CVE-2026-112314 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-112314 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-112314

Explore →

Is Your Infrastructure Affected by CVE-2026-112314?

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