# CVE-2026-78628: Improper Input Validation in the Okta Credential Provider for Windows

> Attackers can trigger memory corruption in the Okta Windows credential provider, causing crashes or leaking adjacent memory into logs.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-mpf7-rw4x-66w7

## What is CVE-2026-78628?

CVE-2026-78628 is a medium-severity memory corruption vulnerability in Okta Credential Provider for Windows, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Okta Credential Provider for Windows does not validate a serialized credential buffer before interpreting it as a Kerberos logon structure. The buffer size and packed string offsets are not checked. Processing a malformed buffer can cause the credential provider process to terminate unexpectedly or lead to out-of-bounds memory reads and writes, which may result in the disclosure of adjacent process memory into local system logs.

Weakness: CWE-787 (Out-of-bounds Write), CWE-20 (Improper Input Validation), CWE-125 (Out-of-bounds Read)

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


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

No fix has been published for CVE-2026-78628 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-78628 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78628 is a medium-severity memory corruption vulnerability in Okta Credential Provider for Windows, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78628 in the wild and no public exploit code.

Affected product: Okta Credential Provider for Windows. 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-78628/ (Markdown: https://insights.sbomify.com/CVE-2026-78628/index.md)
```

## Sources

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

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