Skip to main content
← Vulnerabilities

In JetBrains Junie CLI before 26.8.24 command execution was possible via the Allow Similar Commands option

7.0HighCNA
Exploited
No known exploitation
Fix
Fixed in 26.8.24
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 26.8.24.

Published
Last modified
7/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

In JetBrains Junie CLI before 26.8.24 command execution was possible via the Allow Similar Commands option

cve.now Index

7Pcve.now Index 7 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7/10CVSS 7.0
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 26.8.24.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • JetBrains Junie CLI

    fixed in 26.8.24

Evidence 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-123315

Is CVE-2026-123315 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-123315?

Junie CLI: before 26.8.24.Source: cve.now feed data

How do I fix CVE-2026-123315?

Upgrade to a fixed version: 26.8.24.Source: cve.now feed data