AI Science Tracker

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

stunnel · AI involvement attributed to AISLE AI-native discovery engine (specific model not identified)

Finding and attribution

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.

Product: stunnel. AI system: AISLE AI-native discovery engine (specific model not identified). Team / organization: AISLE; Red Hat.

CVE identifiers: CVE-2026-70367.

AI and human contribution (source account): AISLE’s public CVE index labels this case among findings discovered by its AI-native engine. This is the company’s case-list attribution; the specific model, degree of automation and division of work between AI and people are not identified in the cited sources. The CNA credits: This issue was discovered by Found by AISLE in partnership with Red Hat.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The primary CNA record was published 2026-08-04. The reviewed sources do not establish whether the issue was known to defenders before disclosure or exploited in the wild; this classification does not make a zero-day or non-exploitation claim.

Remediation status: not established. A remediation version or release is not established by the checked case-specific sources. The public disclosure record is linked for reference; patch availability and deployment are not inferred.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 4 Aug 2026. AI attribution date not established by the source. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Medium · highest recorded score 5.4. Documented technical effects: Not available.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

  • CVE-2026-70367: CVSS 3.1 · 5.4 (Medium) · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N. CVE Program CNA record · checked 17 Nov 2026.

Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.

Documented fix: A remediation version or release is not established by the checked case-specific sources. The public disclosure record is linked for reference; patch availability and deployment are not inferred.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases