MIT Kerberos 5 (krb5) through 1.22.2 contains a NULL pointer dereference in make_cred_list() in rd_cred.c that allows authenticated Kerberos clients to crash services by sending mismatched KRB-CRED arrays. Attackers can send forwarded credentials with more tickets than ticket_info entries through gss_accept_sec_context() to crash GSS-API acceptor services, causing denial of service.
CVE-2026-107778
“—” beside the score: it is equal to the CVSS score beside it.
Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-08. A secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.5
- EG Score
- 6.5MEDIUMhigh confidence
- EG Risk
- 29EG Risk 29/100
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 (value × EchelonGraph’s weight)Severity65% × 45%The EG Score, 6.5 of 10.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (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. - EPSS PROB
- 0.4%
- EPSS %ILE
- 34th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (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
October 8, 2026
Last Modified
October 9, 2026
Advisory Details (6)
Auto-updated Oct 8, 2026MIT krb5 through 1.22.2 NULL Pointer Dereference via krb5_rd_cred() | Advisories | VulnCheck
https://www.vulncheck.com/advisories/mit-krb5-through-1.22.2-null-pointer-dereference-via-krb5-rd-credkrb5/src/lib/krb5/krb/rd_cred.c at krb5-1.22.2-final · krb5/krb5 · GitHub
https://github.com/krb5/krb5/blob/krb5-1.22.2-final/src/lib/krb5/krb/rd_cred.c#L77-L112commit 62196e2b2691 (krb5/krb5)
Fix landed in krb5/krb5 commit 62196e2b2691 — awaiting tagged release
https://github.com/krb5/krb5/commit/62196e2b269159a5465f5b8d0ed7cf6f29c3282acommit 48afa9abb89a (krb5/krb5)
Fix landed in krb5/krb5 commit 48afa9abb89a — awaiting tagged release
https://github.com/krb5/krb5/commit/48afa9abb89ab2176bb20624d87d010b9984fc08Validate ticket_info count in KRB-CRED processing
Fix merged in krb5/krb5 PR #1511 on 2026-05-19 — awaiting tagged release
https://github.com/krb5/krb5/pull/1511Vendor Advisories for CVE-2026-107778(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| krb5 | 1.20.1-2 ... 1.22.1-3 (23 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| krb5 | 1.21.3-5 ... 1.22.1-3 (6 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| krb5 | 1.21.3-5, 1.22.1-1, 1.22.1-2, 1.22.1-2.1, 1.22.1-3 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 22× in last 7d / 22× 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 it from the CNA feed. 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). Most recent first.
- 2026-10-12 16:38 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-11 20:14 UTCEG score recompute
- 2026-10-11 18:26 UTCEG score recompute
- 2026-10-11 15:00 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-11 09:07 UTCEG score recompute
- 2026-10-11 09:07 UTCVendor advisory
- 2026-10-11 09:06 UTCGHSA enrichmentGHSA-xfjm-wc9w-mmc6 · GitHub severity HIGH · GitHub CVSS 6.5
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-10 10:49 UTCEG score recompute
- 2026-10-10 10:49 UTCGHSA enrichmentGHSA-xfjm-wc9w-mmc6 · GitHub severity HIGH · GitHub CVSS 6.5
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-09 12:34 UTCEG score recompute
- 2026-10-09 12:34 UTCGHSA enrichmentGHSA-xfjm-wc9w-mmc6 · GitHub severity HIGH · GitHub CVSS 6.5
- 2026-10-09 11:54 UTCEG score recompute
- 2026-10-09 11:53 UTCGHSA enrichmentGHSA-xfjm-wc9w-mmc6 · GitHub severity HIGH · GitHub CVSS 6.5
- 2026-10-08 21:37 UTCEG score recompute
- 2026-10-08 21:37 UTCGHSA enrichmentGHSA-xfjm-wc9w-mmc6 · GitHub severity HIGH · GitHub CVSS 6.5
- 2026-10-08 21:20 UTCEG score recompute
- 2026-10-08 20:23 UTCEG score recomputeFirst assessed: 6.5 MEDIUM
- 2026-10-08 20:23 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownDebian:12:krb5
- CVE-2011-4862EG 10.0EPSS p100HIGH
- CVE-2011-0285EG 10.0EPSS p97HIGH
- CVE-2009-4212EG 10.0EPSS p94HIGH
- CVE-2009-0846EG 10.0EPSS p95HIGH
- CVE-2008-0947EG 10.0EPSS p95HIGH
- CVE-2007-5902EG 10.0EPSS p93HIGH
- CVE-2007-4743EG 10.0EPSS p91HIGH
- CVE-2007-3999EG 10.0EPSS p96HIGH
- CVE-2007-2442EG 10.0EPSS p96HIGH
- CVE-2007-0956EG 10.0EPSS p98HIGH
Frequently asked(5)
What is CVE-2026-107778?
When was CVE-2026-107778 made public?
Is CVE-2026-107778 actively exploited?
What is the CVSS score of CVE-2026-107778?
How do I remediate CVE-2026-107778?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-107778
Is Your Infrastructure Affected by CVE-2026-107778?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.