CVSS 3.1
3.1 lowCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:NCVE-2026-126349
Addressable display_uri can show misleading hosts containing bidi and invisible characters
Low (3.1) in sporkmonger addressable.
On this page
Addressable is an alternative implementation to the URI implementation that is part of Ruby's standard library. From 2.0.0 until 2.9.1, Addressable::IDNA.to_unicode can decode Punycode labels that contain bidirectional controls, zero-width characters, control characters, or other default-ignorable format characters. Addressable::URI#display_uri can consequently show a reordered or visually indistinguishable hostname even though host, normalized_host, and network connections use the original encoded hostname. The pure-Ruby backend accepts the full prohibited set, while the native libidn backend is affected from 2.5.2 for characters added after Unicode 3.2. This issue is fixed in version 2.9.1.
Severity
- CWEs
- CWE-176 Improper Handling of Unicode Encoding
CWE-451 User Interface (UI) Misrepresentation of Critical Information
CWE-1007 Insufficient Visual Distinction of Homoglyphs Presented to User - OWASP Top 10
- A06:2025 Insecure Design
- Published
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-126349 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126349?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126349?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126349 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-126349)
HTML:
<a href="https://cve.bz/cve/CVE-2026-126349"><img src="https://cve.bz/cve/badge/CVE-2026-126349.svg" alt="CVE-2026-126349"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| sporkmonger addressable | >= 2.0.0, < 2.9.1 |
Attack patterns (CAPEC)
- CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High
- CAPEC-632 Homograph Attack via Homoglyphs Likelihood: Low · Severity: Medium
- CAPEC-98 Phishing Likelihood: High · Severity: Very High
- CAPEC-154 Resource Location Spoofing Likelihood: Medium · Severity: Medium
- CAPEC-163 Spear Phishing Likelihood: High · Severity: High
- CAPEC-164 Mobile Phishing Likelihood: High · Severity: High
- CAPEC-173 Action Spoofing Likelihood: High · Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.