How severe is CVE-2022-31249?

CVE-2022-31249 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-31249?

CVE-2022-31249 affects the following packages: github.com/rancher/wrangler (Go), github.com/rancher/wrangler (Go), github.com/rancher/wrangler (Go), github.com/rancher/wrangler (Go). Ecosystems affected: Go.

How do I fix CVE-2022-31249?

Update github.com/rancher/wrangler to 0.7.4-security1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31249 is resolved across your whole dependency graph.

How do I detect CVE-2022-31249 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/wrangler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-31249 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2022-31249 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-31249 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-31249?

CVE-2022-31249 has an EPSS (Exploit Prediction Scoring System) score of 3.8%, placing it in the 90th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-31249?

CVE-2022-31249 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-31249 published, and has it been updated?

CVE-2022-31249 was published on February 7, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2022-31249 — wrangler

HIGHFix: rancher/wrangler@12397ee

CVE-2022-31249 is a high-severity (CVSS 7.5) OS Command Injection vulnerability in github.com/rancher/wrangler. A fix is available for github.com/rancher/wrangler — see the affected versions and patch details below.

[RANCHER] OS command injection in Rancher and Fleet

Also known asGHSA-qrg7-hfx7-95c5GO-2023-1519

Published

Feb 7, 2023

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-31249.

EPSS Exploitation Probability

via FIRST.org ↗

3.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐹github.com/rancher/wrangler🐹github.com/rancher/wrangler🐹github.com/rancher/wrangler🐹github.com/rancher/wrangler

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A command injection vulnerability was discovered in Wrangler's Git package affecting versions up to and including v1.0.0.

Wrangler's Git package uses the underlying Git binary present in the host OS or container image to execute Git operations. Specially crafted commands can be passed to Wrangler that will change their behavior and cause confusion when executed through Git, resulting in command injection in the underlying host.

Workarounds

A workaround is to sanitize input passed to the Git package to remove potential unsafe and ambiguous characters. Otherwise, the best course of action is to update to a patched Wrangler version.

Patches

Patched versions include v1.0.1 and later and the backported tags - v0.7.4-security1, v0.8.5-security1 and v0.8.11.

For more information

If you have any questions or comments about this advisory:

Reach out to SUSE Rancher Security team for security related inquiries.
Open an issue in Rancher or Wrangler repository.
Verify our support matrix and product support lifecycle.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/rancher/wrangler`	all versions	0.7.4-security1`go get github.com/rancher/wrangler@v0.7.4-security1`
🐹Go	`github.com/rancher/wrangler`	≥ 0.8.0&&< 0.8.5-security1	0.8.5-security1`go get github.com/rancher/wrangler@v0.8.5-security1`
🐹Go	`github.com/rancher/wrangler`	≥ 1.0.0&&< 1.0.1	1.0.1`go get github.com/rancher/wrangler@v1.0.1`
🐹Go	`github.com/rancher/wrangler`	≥ 0.8.6&&< 0.8.11	0.8.11`go get github.com/rancher/wrangler@v0.8.11`

Affected Products

1 product · 3 configurations

Application

wranglersuse

≥ 0.8.0 && < 0.8.5

1 version

1.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/wrangler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/rancher/wrangler to 0.7.4-security1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31249 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### Impact A command injection vulnerability was discovered in Wrangler's Git package affecting versions up to and including `v1.0.0`. Wrangler's Git package uses the underlying Git binary present in the host OS or container image to execute Git operations. Specially crafted commands can be passed to Wrangler that will change their behavior and cause confusion when executed through Git, resulting in command injection in the underlying host. ### Workarounds A workaround is to sanitize input passed to the Git package to remove potential unsafe and ambiguous characters. Otherwise, the best co