CVE-2025-67601: Rancher CLI skips TLS verification on Rancher CLI login command

Published Feb 1, 2026
·
Updated

Impact A vulnerability has been identified within Rancher Manager, where using self-signed CA certificates and passing the -skip-verify flag to the Rancher CLI login command without also passing the –cacert flag results in the CLI attempting to fetch CA certificates stored in Rancher’s setting cacerts. This does not apply to any other commands and only applies to the login command if the –cacert flag was not provided.

An attacker with network-level access between the Rancher CLI and Rancher Manager could interfere with the TLS handshake to return a CA they control, despite the use of the --skip-verify flag. This may be abused to bypass TLS as a security control. Attackers can also see basic authentication headers in a Man-in-the-Middle due to the lack of TLS enforcement.

Please consult the associated MITRE ATT&CK - Technique - Man-in-the-Middle for further information about this category of attack.

Patches This vulnerability is addressed by removing the ability to fetch CA certificates stored in Rancher’s setting cacerts when using the login command. Whenever required, for example when using self-signed certificates, CA certificates have to be explicitly passed with the –cacert flag.

Patched versions of Rancher include releases v2.13.2, v2.12.6, v2.11.10, and v2.10.11.

Workarounds If a projecct can't upgrade to a fixed version, please make sure whenever required, for example when using self-signed certificates, to always explicitly pass CA certificates with the –cacert flag when using the login command.

References If there are any questions or comments about this advisory: - Reach out to the SUSE Rancher Security team for security related inquiries. - Open an issue in the Rancher repository. - Verify with the support matrix and product support lifecycle.

Note: Rancher versions beyond 2.3.0-alpha5 are no longer supported at pkg.go.dev, follow Rancher installation instructions for newer versions.

Other sources

A vulnerability has been identified within Rancher Manager, where using self-signed CA certificates and passing the -skip-verify flag to the Rancher CLI login command without also passing the –cacert flag results in the CLI attempting to fetch CA certificates stored in Rancher’s setting cacerts.

MITRE

Affected Software

9 affected componentsFixes available
go/github.com/rancher/rancher>=2.10.0<2.10.11
2.10.11
go/github.com/rancher/rancher>=2.11.0<2.11.10
2.11.10
go/github.com/rancher/rancher>=2.12.0<2.12.6
2.12.6
go/github.com/rancher/rancher>=2.13.0<2.13.2
2.13.2
go/github.com/rancher/rancher<0.0.0-20260129092249-bb0625fd1896
0.0.0-20260129092249-bb0625fd1896
SUSE rancher>=2.10.0<2.10.11
SUSE rancher>=2.11.0<2.11.10
SUSE rancher>=2.12.0<2.12.6
SUSE rancher>=2.13.0<2.13.2

Event History

Feb 1, 2026
Advisory Published
via GitHub·05:58 PM
Data Sourced
via GitHub·05:58 PM
DescriptionSeverityWeaknessAffected Software
Feb 25, 2026
CVE Published
via MITRE·10:36 AM
Data Sourced
via MITRE·10:36 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:16 AM
DescriptionSeverityWeaknessAffected Software
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-2025-67601?

CVE-2025-67601 is considered a moderate severity vulnerability due to the potential risk when using self-signed CA certificates.

2

How do I fix CVE-2025-67601?

To fix CVE-2025-67601, ensure to use the correct version of Rancher, specifically versions 2.10.11, 2.11.10, 2.12.6, or 2.13.2 or later.

3

What systems are affected by CVE-2025-67601?

CVE-2025-67601 affects the Rancher Manager software, particularly when using certain CLI login commands with self-signed certificates.

4

What are the risks of CVE-2025-67601 if not addressed?

If not addressed, CVE-2025-67601 poses a risk of insecure communication and unauthorized access to Rancher services.

5

Is a workaround available for CVE-2025-67601?

A potential workaround for CVE-2025-67601 includes avoiding the use of the -skip-verify flag without the -cacert flag.

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