Skip to main content
CVE-2025-58335VulnerabilityPublished

CVE-2025-58335: JetBrains Junie · CWE-356

Affects JetBrains JunieSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
JetBrains JunieAffected
  • =0
Fixed in–

AI-suggested

European organizations should implement strict access controls to limit local access to systems running JetBrains Junie, ensuring only authorized personnel can interact with the software. Endpoint security solutions should be enhanced to detect and prevent social engineering attempts that could lead to user interaction exploitation. Monitoring and logging of search_project function usage could help detect anomalous behavior indicative of exploitation attempts. Until official patches are released, organizations should consider restricting or disabling the search_project functionality if feasible, or isolate systems running vulnerable versions in secure network segments. Regular user training on phishing and social engineering risks can reduce the likelihood of successful exploitation. Additionally, organizations should maintain an inventory of JetBrains Junie versions in use and plan prompt updates once patches become available. Employing application whitelisting and privilege management can further reduce the attack surface by limiting the ability of unauthorized users to execute or interact with vulnerable components.

Description

In JetBrains Junie before 252.284.66, 251.284.66, 243.284.66, 252.284.61, 251.284.61, 243.284.61, 252.284.50, 252.284.54, 251.284.54, 251.284.50, 243.284.54, 243.284.50 information disclosure was possible via search_project function

References

Community reviews

Loading reviews…