dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-45393

HIGH · 7.8 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cribl Edge for Windows before 4.17.1 has incorrect default permissions on the installer authentication directory (CWE-276), exposing a cryptographic secret used for JWT signing and password-hash derivation. A local authenticated user can read this secret, forge administrative API tokens, and use them to invoke a pipeline function containing an OS command injection (CWE-78) that executes in NT AUTHORITY\SYSTEM context.

MitigationUpgrade Cribl Edge for Windows to version 4.17.1 or later to remediate the permission vulnerability and command injection vector.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Cribl Edge for Windows installation
    Check for Cribl Edge installation by looking in common locations: C:\Program Files\Cribl or C:\Program Files (x86)\Cribl, or check registry key HKLM\SOFTWARE\Cribl\Edge for InstallPath
    Affected if Cribl Edge for Windows is not installed on the system
  2. Determine installed version
    Locate the version file in the installation directory (often version.txt or in the bin folder), or run 'cribl version' from the installation path if CLI is available
    Affected if Installed version is lower than 4.17.1 (e.g., 4.17.0 or earlier)
  3. Identify installer authentication directory
    Locate the directory at path: <InstallPath>\data\installer_auth (or similar path under the Cribl data directory). Use File Explorer or 'dir' command to confirm its existence
    Affected if The installer_auth directory exists on the system
  4. Check directory permissions
    Right-click the installer_auth folder in Windows Explorer, go to Properties > Security, or use 'icacls <path>\installer_auth' from an elevated command prompt to view permissions
    Affected if Users without Administrator or SYSTEM privileges can read contents of this directory, or the directory grants Read permission to the Users group or Authenticated Users
  5. Verify secret file accessibility
    Within the installer_auth directory, attempt to read any .key, .pem, secret, or credential file. Use 'type <filename.ext>' or open in a text editor to confirm content is readable
    Affected if A cryptographic key file or secret is present and readable by a non-elevated user account

A user is affected if Cribl Edge for Windows version is below 4.17.1 AND the installer_auth directory with readable secrets exists on the system, allowing a local authenticated user to obtain JWT signing keys.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cribl Edge for Windows to version 4.17.1 or later to remediate the permission vulnerability and command injection vector.

Recommended fix High confidence

4.17.1

  1. Stop the Cribl Edge service on the Windows host
  2. Backup the current Cribl Edge installation and configuration data
  3. Download Cribl Edge version 4.17.1 or later from the official Cribl download site (docs.cribl.io)
  4. Run the installer for version 4.17.1 or later
  5. Follow the upgrade prompts, ensuring to preserve existing configuration
  6. Restart the Cribl Edge service
  7. Verify the upgrade was successful by checking the Cribl Edge version in the UI or CLI
Caveat Review release notes for any configuration changes between current version and 4.17.1

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45393 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45393 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data