# CVE-2026-107778: MIT krb5 through 1.22.2 NULL Pointer Dereference via krb5_rd_cred()

> Authenticated attackers can crash GSS-API services by sending malformed credential arrays, causing denial of service in MIT Kerberos 5.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** AZL-106839, BELL-CVE-2026-107778, CLSA-2026-1792097614, DEBIAN-CVE-2026-107778, ECHO-6499-594d-ef91, GHSA-xfjm-wc9w-mmc6, OESA-2026-4494, ROOT-OS-DEBIAN-12-CVE-2026-107778, ROOT-OS-DEBIAN-13-CVE-2026-107778, UBUNTU-CVE-2026-107778, openSUSE-SU-2026:12296-1

## What is CVE-2026-107778?

CVE-2026-107778 is a high-severity vulnerability in MIT krb5, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-107778?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `krb5` | openSUSE:Tumbleweed | All versions | 1.22.2-5.1 |

## How do I fix CVE-2026-107778?

Apply the vendor's patch.

## Is CVE-2026-107778 being exploited?

There is no known exploitation of CVE-2026-107778 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107778 and fix it if it is affected.

What it is: CVE-2026-107778 is a high-severity vulnerability in MIT krb5, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107778 in the wild and no public exploit code.

Affected product: MIT krb5. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107778/ (Markdown: https://insights.sbomify.com/CVE-2026-107778/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107778
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107778
- OSV: https://osv.dev/vulnerability/CVE-2026-107778

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107778/
Summaries are generated and may contain mistakes; the official description above is the record.