CVE-2026-126354: sporkmonger addressable · Path Traversal
Affects sporkmonger addressableSource CVE Database V5
Not known to be exploited · CVSS 4.8 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 | 4.8 |
|---|
- Patch
- Available – fixed in 2.9.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation 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 to Addressable version 2.9.1 or later, where this path traversal issue is fixed. Applications should ensure that the same normalized URI value is used consistently for both authorization checks and resource access, or reject URIs containing parent directory segments to prevent bypass.
Description
A path traversal vulnerability (CWE-22) exists in the Addressable Ruby library versions 2.2.5 through 2.9.0. The normalize_path method can resolve paths with parent segments differently than an RFC 3986 resolver, potentially allowing unauthorized access outside intended path allowlists. This issue is fixed in version 2.9.1.