stoatchat versions before 0.15.0 fail to block the IPv6 unspecified address (::) in the SSRF blocklist, allowing unauthenticated attackers to bypass protections via the /proxy and /embed endpoints. Attackers can craft requests using IPv6 literal syntax to access services on the loopback interface and retrieve sensitive internal content.
CVE-2026-73058
Score 5.8 from GitHub Security Advisory published 2026-08-16. a secondary CVSS source baseline 5.8; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.8
- EG Score
- 5.8(high)
- EG Risk
- 57(Attend)EG Risk 57/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity58% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 15%
- KEV
- Not listed
Published
August 16, 2026
Last Modified
August 17, 2026
Advisory Details (2)
Auto-updated Aug 16, 2026stoatchat before 0.15.0 SSRF via IPv6 unspecified address bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/stoatchat-before-ssrf-via-ipv6-unspecified-address-bypassUnauthenticated SSRF via IPv6 unspecified address (::) bypass · Advisory · stoatchat/stoatchat · GitHub
https://github.com/stoatchat/stoatchat/security/advisories/GHSA-4rmr-77qv-hq47Vendor Advisories for CVE-2026-73058(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 15:56 UTCEG score recompute
- 2026-08-20 15:56 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 16:27 UTCGHSA enrichment
- 2026-08-18 16:59 UTCEG score recompute
- 2026-08-18 16:59 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 17:28 UTCEG score recompute
- 2026-08-17 17:28 UTCGHSA enrichment
- 2026-08-17 17:11 UTCEG score recompute
- 2026-08-17 17:11 UTCGHSA enrichment
- 2026-08-17 14:04 UTCEG score recompute
- 2026-08-17 14:04 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:36 UTCEG score recompute
- 2026-08-16 13:27 UTCEG score recompute
- 2026-08-16 13:26 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-73058?
When was CVE-2026-73058 disclosed?
Is CVE-2026-73058 actively exploited?
What is the CVSS score of CVE-2026-73058?
How do I remediate CVE-2026-73058?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-73058
Is Your Infrastructure Affected by CVE-2026-73058?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.