Rancher agents can be hijacked by taking over the Rancher Server URL

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.0 · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

EPSS

• CVE-2024-22030: 0.42% estimated exploitation activity in the next 30 days; percentile 36.63 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact A vulnerability has been identified within Rancher that can be exploited in narrow circumstances through a man-in-the-middle (MITM) attack. An attacker would need to have control of an expired domain or execute a DNS spoofing/hijacking attack against the domain to exploit this vulnerability. The targeted domain is the one used as the Rancher URL. SUSE is unaware of any successful exploitation of this vulnerability, which has a high complexity bar. Please consult the associated MITRE ATT&CK - Technique - Adversary-in-the-Middle for further information about this attack category. Patches A new setting, agent-tls-mode, was added, which allows users to specify if agents will use strict certificate verification when connecting to Rancher. The field can be set to strict (which requires the agent to verify the certificate using only the Certificate Authority in the cacerts setting) or system-store (which allows the agent to verify the certificate using any Certificate Authority in…

Published by the source

26 Sep 2024, 21:13 UTC

Last modified by the source

16 Oct 2024, 17:26 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h4h5-9833-v2p4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-22030

Advisory: Rancher agents can be hijacked by taking over the Rancher Server URL
IDs: CVE-2024-22030, GHSA-h4h5-9833-v2p4
Record: https://patchnext.com/advisories/cve-2024-22030 (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/rancher/rancher 2.9.2, 2.8.8, 2.7.15. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/rancher/rancher: affected >= 2.7.0, < 2.7.15; >= 2.8.0, < 2.8.8; >= 2.9.0, < 2.9.2; fixed in 2.7.15, 2.9.2, 2.8.8

## Suggested inspection (read-only)
- Go github.com/rancher/rancher: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/rancher/rancher.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h4h5-9833-v2p4 (GitHub-reviewed advisory GHSA-h4h5-9833-v2p4 lists affected ranges: Go github.com/rancher/rancher >=2.7.0 =2.8.0 =2.9.0 <2.9.2)

Commands are suggestions: review each one before running it.