CVE-2026-133192

Junie GitHub Action could process untrusted fork code in privileged workflows

JetBrains · Junie GitHub Action

First documented disclosure · Review checkpoint

Summary

Untrusted fork code could cross into a privileged workflow run.

Severity and exploitation evidence

Medium · 4.2/10 · CVSS 3.1. Severity source.

Exploitation not established: Malicious exploitation is not established by the reviewed originals. Public demonstrations and catalog absence do not establish exploitation status.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The vendor identifies unsafe processing of fork code without publishing a detailed workflow trace.

Conditions required

An affected privileged workflow processes attacker-controlled fork code; the vendor scores user interaction and high attack complexity.

Potential impact

The workflow's accessible information and state can be exposed or changed.

Affected versions and configurations

Junie GitHub Action: Before 1.10.0.

Fix and mitigation status

1.10.0.

Practical next steps

Apply the issue-specific correction: 1.10.0.

Operating lesson

Separate untrusted repository content from privileged workflow execution.

Evidence and limits

Earliest reviewed public evidence 2026-11-19; CVE publication 2026-11-19. CVSS 3.1 4.2 is attributed to JetBrains in the CNA record. Vendor records are brief and do not disclose a complete attack trace. November 19 is the verified publication date; release-like version numbers are not treated as disclosure dates.

Sources