CVE-2026-92892 json
Potential command execution on the host running JFrog CLI.
published 29d ago modified 20d ago also EUVD-2026-98979
- cvss
- 9.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
Potential arbitrary code execution under specific configurations. Updated October 22, 2026: Affected versions now include JFrog CLI v2.127.0. For remediation, update to v2.128.0 or later.
Patch / fix
- jfrog jfrog-cli 2.128.0
- jfrog-cli openSUSE Tumbleweed 2.127.0-1.1
opensuse advisories openSUSE-SU-2026:12130-1
Is CVE-2026-92892 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-92892 updated cvss 9.0
github.com/jfrog/jfrog-cli: Potential command execution on the host running JFrog CLI.
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 26d ago
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H |
Affected products
- jfrog jfrog-cli
Classification
- Weakness
-
- CWE-88 Improper Neutralization of Argument Delimiters in a Command
References
-
docs.jfrog.com
/releases/docs/jfrog-security-advisories
vendor-advisory
-
github.com
/jfrog/jfrog-cli/releases
vendor-advisory
Sources
- CVE List CVE-2026-92892
- NVD CVE-2026-92892
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.