# CVE-2023-32198: Steve doesn’t verify a server’s certificate and is susceptible to man-in-the-middle (MitM) attacks

> Steve library fails to validate server certificates by default, enabling man-in-the-middle attacks against services using it.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-95fc-g4gj-mqmx, GO-2025-3648

## What is CVE-2023-32198?

CVE-2023-32198 is a high-severity vulnerability in SUSE steve, published on 15 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability has been identified in Steve where by default it was using an insecure option that did not validate the certificate presented by the remote server while performing a TLS connection. This could allow the execution of a man-in-the-middle (MitM) attack against services using Steve.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2023-32198?

10 open source packages ship an affected version, including github.com/rancher/steve.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/rancher/steve` | Go | All versions | None |
| `github.com/rancher/steve` | Go | From 0.2.0 | 0.2.1, 0.4.4, 0.5.13 |
| `github.com/rancher/steve` | Go | From 0.2.0 | 0.2.1 |
| `github.com/rancher/steve` | Go | From 0.2.0 | 0.2.1 |
| `github.com/rancher/steve` | Go | From 0.3.0 | 0.3.3 |
| `github.com/rancher/steve` | Go | From 0.3.0 | 0.3.3 |
| `github.com/rancher/steve` | Go | From 0.4.0 | 0.4.4 |
| `github.com/rancher/steve` | Go | From 0.4.0 | 0.4.4 |
| `github.com/rancher/steve` | Go | From 0.5.0 | 0.5.13 |
| `github.com/rancher/steve` | Go | From 0.5.0 | 0.5.13 |

## How do I fix CVE-2023-32198?

Upgrade github.com/rancher/steve to a fixed version for your release line: 0.2.1, 0.4.4, 0.5.13 or 0.3.3.

## Is CVE-2023-32198 being exploited?

There is no known exploitation of CVE-2023-32198 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32198 and fix it if it is affected.

What it is: CVE-2023-32198 is a high-severity vulnerability in SUSE steve, published on 15 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-32198 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/rancher/steve (Go): affected all versions; no fix listed
- github.com/rancher/steve (Go): affected from 0.2.0; fixed in 0.2.1, 0.4.4, 0.5.13
- github.com/rancher/steve (Go): affected from 0.2.0; fixed in 0.2.1
- github.com/rancher/steve (Go): affected from 0.2.0; fixed in 0.2.1
- github.com/rancher/steve (Go): affected from 0.3.0; fixed in 0.3.3
- github.com/rancher/steve (Go): affected from 0.3.0; fixed in 0.3.3
- github.com/rancher/steve (Go): affected from 0.4.0; fixed in 0.4.4
- github.com/rancher/steve (Go): affected from 0.4.0; fixed in 0.4.4
- github.com/rancher/steve (Go): affected from 0.5.0; fixed in 0.5.13
- github.com/rancher/steve (Go): affected from 0.5.0; fixed in 0.5.13

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-32198/ (Markdown: https://insights.sbomify.com/CVE-2023-32198/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-32198
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-32198
- OSV: https://osv.dev/vulnerability/CVE-2023-32198

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-32198/
Summaries are generated and may contain mistakes; the official description above is the record.