CVE Intelligence
High Cryptography

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

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.

Published Oct 15, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: suse

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
SUSE
Steve and 1 more
CVSS base
8.0
High · 3 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Go Github.com/rancher/steve: fixed in version 0.2.1 — github.com (GitHub Security Advisories)
  • Go Github.com/rancher/steve: fixed in version 0.4.4 — github.com (GitHub Security Advisories)
  • Go Github.com/rancher/steve: fixed in version 0.5.13 — github.com (GitHub Security Advisories)
  • Go Github.com/rancher/steve: fixed in version 0.3.3 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (SUSE Steve, Go Github.com/rancher/steve).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (cryptography), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
SUSE Steve ≥ 0.2.0 and < 0.2.1≥ 0.3.0 and < 0.3.3≥ 0.4.0 and < 0.4.4≥ 0.5.0 and < 0.5.13 Vulnerable CVE Program (cve.org) e CISA ADP
Go Github.com/rancher/steve ≥ 0.2.0 and < 0.2.1≥ 0.4.0 and < 0.4.4≥ 0.5.0 and < 0.5.13≥ 0.3.0 and < 0.3.3 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.0 CVSS 3.1 High 1.3 6.0 meissner@suse.de via NIST National Vulnerability Database
8.0 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
8.0 CVSS 3.1 High — — suse via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H (score shown at the top: meissner@suse.de)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-295 · Improper Certificate Validation

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Check TLS negotiations and unexpected certificates in the component’s traffic.
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 15, 2026 · GitHub Security Advisories
  • Affected products added · go/github.com/rancher/steve
    Oct 15, 2026 · GitHub Security Advisories
  • Affected products added · suse/steve
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • CVSS changed · 8.0
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · Alertas do Telegram
  • CVE published
    Oct 15, 2026 · suse

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 15, 2026 – Oct 15, 2026
  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

4 on the record

Elsewhere on this site

SUSE
every CVE for this vendor
Cryptography
same class
CWE-295
other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2023-32198 is "Steve doesn’t verify a server’s certificate and is susceptible to man-in-the-middle (MitM) attacks", rated High. It affects Steve (SUSE); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.0 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.