CVE-2026-35386

Published Apr 2, 2026
·
Updated

In OpenSSH before 10.3, command execution can occur via shell metacharacters in a username within a command line. This requires a scenario where the username on the command line is untrusted, and also requires a non-default configurations of % in ssh_config.

Affected Software

2 affected componentsFixes available
Microsoft azl3 openssh 9.8p1-5
OpenBSD OpenSSH<10.3

Event History

Apr 2, 2026
CVE Published
via MITRE·04:44 PM
Data Sourced
via MITRE·04:44 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·06:02 PM
DescriptionSeverityAffected Software
Apr 4, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:02 AM
Severity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-35386?

CVE-2026-35386 is classified with a high severity due to the potential for command execution through untrusted usernames.

2

How do I fix CVE-2026-35386?

To mitigate CVE-2026-35386, upgrade to OpenSSH version 10.3 or later, which addresses this vulnerability.

3

Who is affected by CVE-2026-35386?

CVE-2026-35386 affects OpenSSH versions prior to 10.3, specifically configurations that allow untrusted usernames.

4

What causes CVE-2026-35386?

CVE-2026-35386 is caused by improper handling of shell metacharacters in usernames when using OpenSSH.

5

Is CVE-2026-35386 remotely exploitable?

Yes, CVE-2026-35386 can be remotely exploited if the conditions of untrusted usernames and specific ssh_config settings are met.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203