Wails: wildcardPatternToRegex allows Origin bypass via suffix match in BindingsAllowedOrigins
- Exploited
- No known exploitation
- Fix
- Fixed in 2.13.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.13.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
Wails, a framework for building desktop applications with Go and web technologies, has a flaw in how it checks origins for bound Go methods, so an attacker-controlled lookalike origin can invoke those methods remotely, without logging in, if the user visits or interacts with that origin. The resulting impact depends on what the application's bound methods expose, and the bug only occurs when the app uses a trailing or partial-label wildcard directly after an allowed domain, with the issue fixed in a later release.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Wails is a framework for building desktop applications using Go and web technologies. From 2.0.0 until 2.13.0, BindingsAllowedOrigins in v2/internal/frontend/originvalidator/originValidator.go passes wildcard patterns to wildcardPatternToRegex, which expands every asterisk to an unrestricted regular-expression match. When an application configures a trailing or partial-label wildcard immediately after an allowed domain, an attacker-controlled lookalike origin can match the allowed suffix and invoke bound Go methods through IPC. A complete-component subdomain wildcard is an unaffected configuration. The resulting confidentiality, integrity, and availability impact depends on the file, database, command, credential, or other operations exposed by the application's bound methods. This issue is fixed in version 2.13.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach10/20Affects Go packages
- Severity7.6/10CVSS 7.6
- No patch0/5No signal
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 40 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.13.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- wailsapp wails
From 2.0.0 · fixed in 2.13.0
- github.com/wailsapp/wails/v2Go
From 2.0.0 · fixed in 2.13.0
Evidence 5
- Advisory
- Exploit
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-34157
Is CVE-2026-34157 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-34157?
wails: from 2.0.0 before 2.13.0. github.com/wailsapp/wails/v2 (Go): from 2.0.0 before 2.13.0.Source: cve.now feed data
How do I fix CVE-2026-34157?
Upgrade to a fixed version: 2.13.0.Source: cve.now feed data