OpenSSH Certificate Bug Enables Root Bypass
A flaw in OpenSSH's handling of comma characters in certificate principals lets attackers with a trusted CA certificate authenticate as root.
Sourcecisecurity.org — open the original
What to check
- Applies to
- The 1 CVE named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
CISA's MS-ISAC issued an advisory on CVE-2026-35414, a vulnerability in OpenSSH versions prior to 10.3 affecting how the authorized_keys principals option processes certificate principal names. When a Certificate Authority's certificate principal list contains comma characters in specific configurations, OpenSSH's access control logic can be bypassed, allowing an attacker holding a valid certificate from a trusted CA to authenticate as root on the affected server.
The issue was identified by researcher Cyera, who successfully demonstrated exploitation using a test certificate and test server, though there is no indication of active exploitation in the wild. Because OpenSSH is broadly deployed for remote administration across virtually all sectors, successful exploitation could grant an attacker root access to any server running the vulnerable configuration, making this a high-impact issue for environments relying on certificate-based SSH authentication with CA-signed principals.
Organizations running affected OpenSSH versions should prioritize patching to 10.3 or later, apply least-privilege principles to limit blast radius, and review CA-issued certificate principal configurations for unusual comma usage as a mitigating step pending patch deployment.
Mentioned in this report
Source reporting: https://www.cisecurity.org/advisory/a-vulnerability-in-openssh-could-allow-for-authentication-bypass_2026-040
Free public brief. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them, no card.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,436 reports from 149 sources, 661 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs