Skip to content
major vulnerability· requires attention

RCE in widely used developer tool (JFrog CLI) with CVSS 9.0 — can compromise developer machines and CI/CD infrastructure.

Applications

CVE-2026-92892

9.0
Critical
EPSS 0.34%Patch availableOct 15, 2026

Remote code execution in JFrog CLI via specific configurations.

common questions

Is CVE-2026-92892 being exploited?

Not confirmed. CVE-2026-92892 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-92892?

CVE-2026-92892 is rated Critical with a CVSS score of 9.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-92892?

Yes. A fix has been recorded for CVE-2026-92892. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-92892 affect?

CVE-2026-92892 affects JFrog CLI (jfrog-cli), Developer workstations, CI/CD build agents. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-92892?

Update jfrog-cli to the patched release, audit CI agents, rotate credentials.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
JFrog CLI (jfrog-cli)Developer workstationsCI/CD build agents
impact

Remote arbitrary code execution via argument/command injection in jfrog-cli, enabling full system or CI/CD agent compromise.

action required

Immediate action required

affected versions
jfrog jfrog-cli
  • affected<= 2.126.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free