Skip to main content
CVE-2026-70367VulnerabilityPublished Updated

SUSE · Security update for stunnel

Affects SUSESource GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-70367· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium : upgrade SUSE stunnel to 5.80 when convenient.

Data as of 10 Nov 2026, 20:18 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.15.4
Patch
Available – fixed in 5.80
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade stunnel to 5.80.

Affected software

ProductAffectedFixed in
Mobi-Com Polska Sp. z o.o.stunnelAffected
  • >=5.25 <5.80
Fixed in
  • 5.80
GitHubstunnelpkg:github/stunnelOther threatsAffected
  • >=5.25 <5.80
Fixed in
  • 5.80

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the security update provided by the SUSE Product Security Team for stunnel to remediate these vulnerabilities. Since this is an official security update, deploying the patch will address the issues.

Description

This security update for stunnel addresses two vulnerabilities: CVE-2026-70367, which involves incomplete IP address filtering in SOCKS proxy mode allowing localhost restriction bypasses, and CVE-2026-70368, where oversized log messages in logging routines can cause stack out-of-bounds reads.

References

Community reviews

Loading reviews…