Skip to content
Fencer Intel
high 7.4

CVE-2026-123852 json

In JetBrains Junie GitHub Action before 1.8.0 code execution with workflow credentials was possible via fork updates

published 3d ago modified 3d ago also EUVD-2026-118355

cvss
7.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

In JetBrains Junie GitHub Action before 1.8.0 code execution with workflow credentials was possible via fork updates

Patch / fix

  • JetBrains Junie GitHub Action 1.8.0

Is CVE-2026-123852 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 Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
3d ago

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

  • JetBrains Junie GitHub Action

Classification

Weakness

References

Sources

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.