CVE-2026-9106: enterprise server before 3.16.20 (exclusive), from 3.17.0 (inclusive), before 3.17.17 (exclusive), from 3.18.0…

Affected technology

enterprise server · before 3.16.20 (exclusive)
github

enterprise server · from 3.17.0 (inclusive), before 3.17.17 (exclusive)
github

enterprise server · from 3.18.0 (inclusive), before 3.18.11 (exclusive)
github

enterprise server · from 3.19.0 (inclusive), before 3.19.8 (exclusive)
github

enterprise server · from 3.20.0 (inclusive), before 3.20.4 (exclusive)
github

enterprise server · from 3.21.0 (inclusive), before 3.21.2 (exclusive)
github

Enterprise Server · 3.17.0 through 3.17.16; status changes: 3.17.17 — unaffected, 3.18.0 through 3.18.10; status changes: 3.18.11 — unaffected, 3.19.0 through 3.19.7; status changes: 3.19.8 — unaffected, 3.20.0 through 3.20.3; status changes: 3.20.4 — unaffected, 3.21.0 through 3.21.1; status changes: 3.21.2 — unaffected, 3.16.0 through 3.16.19; status changes: 3.16.20 — unaffected
GitHub

Component: Not specified by the source

Attack conditions (Vendor/CNA, CVSS 4.0): Network (remote) · Low privileges required · Active user interaction

What an attacker can do

An attacker could exploit this by creating an OAuth application requesting the manage_runners:org scope and directing a victim user to authorize it, as the scope was not displayed on the authorization consent screen. Vendor/CNA’s CVSS 4.0 assessment (base score 4.8/10) rates confidentiality, integrity and availability impact as low.