# CVE-2026-70367: Stunnel: ssrf bypass in stunnel socks proxy via ipv4-mapped ipv6 loopback and unspecified addresses allows access to loopback-only services

CVE-2026-70367 is fixed in stunnel on 1 platform, first by DEBIAN-CVE-2026-70367, released August 8, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-70367
- Priority: Routine
- CVSS: 5.4 (Moderate)
- EPSS: 0.0022
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Aug 4, 2026
- Weakness: Server-Side Request Forgery (SSRF)
- Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70367

## Description

A Server-Side Request Forgery (SSRF) bypass vulnerability exists in “stunnel” 5.79 and lower when configured in SOCKS proxy mode. This flaw allows a client to bypass intended localhost restrictions by using IPv4-mapped IPv6 addresses (e.g., “::ffff:127.0.0.1”) or unspecified addresses ("0.0.0.0", "::"), enabling access to loopback-only services on the "stunnel" host that should not be network-reachable.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | stunnel Debian 14 | 3:5.80-1 | [DEBIAN-CVE-2026-70367](https://patchblox.com/security/data/fix/linux/debian-cve-2026-70367.md) | Aug 8, 2026 |
| Linux | stunnel opensuse-leap 16.0 | 5.74-160000.3.1 | [OPENSUSE-SU-2026:22088-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22088-1.md) | Nov 7, 2026 |
| Linux | stunnel sles 15.7 | 5.70-150600.3.6.1 | [SUSE-SU-2026:4617-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4617-1.md) | Nov 7, 2026 |
| Linux | stunnel sles 16.0 | 5.74-160000.3.1 | [SUSE-SU-2026:24232-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24232-1.md) | Nov 7, 2026 |

---

Data as of 2026-11-08T00:53:09Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.