CVE-2026-70367
Received Received - Intake

SSRF Bypass in Stunnel via IPv4-Mapped IPv6

Vulnerability report for CVE-2026-70367, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-04

Last updated on: 2026-08-04

Assigner: Red Hat, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-04
Last Modified
2026-08-04
Generated
2026-08-04
AI Q&A
2026-08-04
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
stunnel stunnel to 5.80 (exc)
stunnel stunnel 5.79
stunnel stunnel 5.72-8.el10

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-70367 is a Server-Side Request Forgery (SSRF) bypass vulnerability in stunnel versions 5.79 and lower when configured in SOCKS proxy mode. It allows attackers to bypass intended localhost restrictions by using IPv4-mapped IPv6 addresses like ::ffff:127.0.0.1 or unspecified addresses such as 0.0.0.0 or ::. This enables access to loopback-only services on the stunnel host that should not be network-reachable.

Detection Guidance

Check if stunnel is running in SOCKS proxy mode by inspecting its configuration file for 'protocol = socks'. Verify if the SOCKS listener is exposed to untrusted networks using netstat or ss commands like 'ss -tulnp | grep stunnel' or 'netstat -tulnp | grep stunnel'.

Test for vulnerable addresses by attempting to connect to loopback services via IPv4-mapped IPv6 (::ffff:127.0.0.1) or unspecified addresses (0.0.0.0, ::) using tools like curl or nc. Monitor logs for unusual access attempts to localhost-bound services.

Impact Analysis

This vulnerability allows attackers who can reach the SOCKS listener to bypass localhost restrictions and access loopback-only services on the stunnel host. This could lead to exposure of administrative or metadata services, unauthorized access to protected resources, and potential limited integrity or availability disruption.

Mitigation Strategies

Disable the SOCKS proxy mode in stunnel if not required by removing or commenting out 'protocol = socks' in the configuration file and restarting stunnel.

Restrict access to the SOCKS listener by binding it to localhost (127.0.0.1) or a trusted internal IP using the 'accept' directive in the configuration.

Enforce client authentication for the SOCKS proxy to limit unauthorized access until a patch is applied.

Isolate stunnel in a container with no local services or network access to loopback-only resources as an additional precaution.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-70367. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart