CVE-2026-126351: sporkmonger addressable · Inefficient Algorithmic Complexity
Affects sporkmonger addressableSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 2.9.1 when convenient.
Data as of 12 Nov 2026, 22:38 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.9 |
|---|
- Patch
- Available – fixed in 2.9.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade sporkmonger addressable to 2.9.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| sporkmongeraddressable | Affected
| Fixed in
|
AI-suggested
Upgrade Addressable to version 2.9.1 or later, where the inefficient algorithmic complexity issue in normalize_path is fixed. No other mitigation is necessary as the vulnerability is resolved in the official fix.
Description
Addressable is a Ruby library for URI handling. Versions prior to 2.9.1 contain an inefficient algorithmic complexity issue in the normalize_path method, causing quadratic processing time when handling long attacker-controlled URIs. This can lead to denial of service by consuming worker threads. The issue affects methods that normalize, compare, or join URIs but not URI.parse alone or code that does not normalize untrusted URIs. The vulnerability is fixed in version 2.9.1.