dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-45391

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 command injection vulnerability in Cribl Edge for Linux versions 3.2.0 through 4.17.0 allows a local unprivileged user to execute arbitrary commands in the context of the Cribl Edge service account.

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 · moderate confidence

A command injection vulnerability in Cribl Edge for Linux versions 3.2.0 through 4.17.0 allows a local unprivileged user to execute arbitrary commands in the context of the Cribl Edge service account. This is a local privilege escalation vulnerability where improper input handling in a privileged code path permits injection of shell commands.

MitigationUpgrade to Cribl Edge version 4.17.1 or later which contains the fix for this command injection vulnerability. As an interim measure, restrict local user access to the system and monitor for suspicious process activity under the Cribl Edge service account.

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 is installed
    Run 'which cribl' or check for /opt/cribl directory, or use 'systemctl list-units | grep cribl' to find the service
    Affected if Cribl Edge is not present on the system - not affected
  2. Determine installed Cribl Edge version
    Run 'cribl version' or check /opt/cribl/version.txt, or use 'systemctl status cribl-edge' to see version info
    Affected if Version is between 3.2.0 and 4.17.0 inclusive - likely affected
  3. Confirm Cribl Edge service is running
    Run 'systemctl is-active cribl-edge' or 'ps aux | grep cribl'
    Affected if Service is not running - not currently exploitable, but still vulnerable when started
  4. Check user privileges to Cribl directories
    Run 'ls -la /opt/cribl' and 'ls -la /etc/cribl' to inspect file ownership and permissions
    Affected if Non-root users have write access to Cribl configuration or binary directories - could enable exploitation

System is affected if Cribl Edge version 3.2.0 through 4.17.0 is installed and the service is running or could be started, allowing a local unprivileged user to potentially inject commands.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Cribl Edge version 4.17.1 or later which contains the fix for this command injection vulnerability. As an interim measure, restrict local user access to the system and monitor for suspicious process activity under the Cribl Edge service account.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45391 — 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-45391 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