CVE
Addressable spoofed hostname display in display_uri method
- Exploited
- No known exploitation
- Fix
- Fixed in 2.9.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.9.1.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.24% · 15th percentile
- 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? →
- 20/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Addressable, a Ruby library for parsing and handling URIs, can display a misleading hostname through its display_uri method when the hostname is Punycode-encoded with bidirectional, zero-width, or other invisible characters. An attacker can exploit this remotely without logging in, but only if a user takes action, such as clicking a crafted link, and the result is a deceptive display rather than a change to the host actually contacted.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
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 RubyGems packages
- Severity3.1/10CVSS 3.1
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.9.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126349 (Addressable display_uri can show misleading hosts containing bidi and invisible characters), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126349 (entry last updated 2026-11-12):
Affected:
- sporkmonger addressable: from 2.0.0, fixed in 2.9.1
- RubyGems package addressable: from 2.0.0, fixed in 2.9.1
Fixed versions: 2.9.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126349 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126349 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (RubyGems): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/sporkmonger/addressable/security/advisories/GHSA-539f-xcgw-2gjg
- https://github.com/sporkmonger/addressable/commit/60455d32bb59fda2585a0e1865a9fcb21e8e55b1
- https://github.com/sporkmonger/addressable/releases/tag/addressable-2.9.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126349
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126349"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- sporkmonger addressable
From 2.0.0 · fixed in 2.9.1
- addressableRubyGems
From 2.0.0 · fixed in 2.9.1
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126349
Is CVE-2026-126349 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-126349?
addressable: from 2.0.0 before 2.9.1. addressable (RubyGems): from 2.0.0 before 2.9.1.Source: cve.now feed data
How do I fix CVE-2026-126349?
Upgrade to a fixed version: 2.9.1.Source: cve.now feed data