Quick answers
- Is CVE-2026-35386 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35386 being exploited in the wild.
- How severe is CVE-2026-35386?
- Low severity, with a CVSS score of 3.6, published 2 April 2026.
- Which products and versions are affected?
- OpenBSD Openssh before 10.3.
- Is there a fix for CVE-2026-35386?
- A patch was published on 2026-04-02: Fixed in OpenSSH 10.3/10.3p1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35386 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-35386?
- Check whether you run OpenBSD Openssh at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A command injection vulnerability exists in OpenSSH client (ssh) versions prior to 10.3. The flaw is caused by insufficient validation of shell metacharacters in usernames supplied via the command line, which are processed too late to prevent expansion from %-tokens (such as %u) in ssh_config. An attacker who can control the username passed to the ssh command can achieve arbitrary command execution if the configuration uses these tokens within a 'Match exec' block. This is considered a low-severity issue as it requires a non-default configuration and the ability to provide untrusted input to the command-line arguments. The issue is addressed in OpenSSH 10.3.
Affected products
- OpenBSD OpenSSH before 10.3
Timeline
- 2026-04-02: disclosed
- 2026-04-02: patched: Fixed in OpenSSH 10.3/10.3p1