---
id: "CVE-2026-123852"
page: "https://infrastack.ai/live/CVE-2026-123852"
kind: "vulnerability"
aliases: ["CVE-2026-123852"]
title: "JetBrains Junie GitHub Action: fork updates let code run with workflow credentials"
severity: "high"
cvss: 7.4
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["ci", "github-actions", "jetbrains", "junie", "package"]
not_affected_if: ["action-not-used", "version-1.8.0-or-later"]
published_at: "2026-11-06T17:17:24+00:00"
first_seen_at: "2026-11-06T17:43:13+00:00"
updated_at: "2026-11-06T17:45:06+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-123852", "first_seen_at": "2026-11-06T17:43:13+00:00"}]
exploit_sources: []
---

# JetBrains Junie GitHub Action: fork updates let code run with workflow credentials

Link for people: https://infrastack.ai/live/CVE-2026-123852 (this .md is for agents)

Before version 1.8.0, the JetBrains Junie GitHub Action allowed code execution with the workflow's credentials when a fork was updated. An attacker who can push changes through a fork can run code with the secrets available to the workflow.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Look for uses of the JetBrains Junie GitHub Action in workflow files under `.github/workflows`
- Check the pinned action version; anything below `1.8.0` is affected per the sources
- Review which secrets and tokens the workflow exposes when triggered by fork pull requests

## Fix

- JetBrains Junie GitHub Action: upgrade to `1.8.0` or later

## Timeline

- 2026-11-06T17:43:13+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-123852

## From the sources

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

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_