# CVE-2026-45393: Local privilege escalation to SYSTEM in Cribl Edge for Windows

> Local attackers can escalate privileges to SYSTEM by exploiting insecure permissions to forge tokens and execute OS commands.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-2hpj-h2fj-2jg5

## What is CVE-2026-45393?

CVE-2026-45393 is a high-severity vulnerability in Cribl Edge, published on 12 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability chain in Cribl Edge for Windows before 4.17.1 allows a local authenticated user to escalate privileges to NT AUTHORITY\SYSTEM. Incorrect default permissions on the Windows installer's authentication directory (CWE-276) expose a cryptographic secret used for JWT signing and password-hash derivation, enabling forgery of administrative API tokens. The forged token can then be used to invoke a pipeline function that reaches an OS command sink (CWE-78) running in the SYSTEM context.

Weakness: CWE-20 (Improper Input Validation), CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-276 (Incorrect Default Permissions)

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


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

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

## Is CVE-2026-45393 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45393 is a high-severity vulnerability in Cribl Edge, published on 12 May 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-45393 in the wild and no public exploit code.

Affected product: Cribl Edge. 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-45393/ (Markdown: https://insights.sbomify.com/CVE-2026-45393/index.md)
```

## Sources

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

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