Skip to main content
VulnerabilityPublished

CVE-2026-126353: sporkmonger addressable · ReDoS

Affects sporkmonger addressableSource CVE Database V5

0
Compare

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

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
sporkmongeraddressableAffected
  • >=2.3.0 <2.9.1
Fixed in
  • 2.9.1

AI-suggested

Upgrade Addressable to version 2.9.1 or later, where this vulnerability is fixed. No other mitigation is indicated or required.

Description

Addressable, a Ruby URI implementation alternative, has a vulnerability in versions 2.3.0 through 2.9.0 where certain URI template expressions with multiple exploded variables produce ambiguous regular expressions. This ambiguity can cause Template#match or Template#extract to consume excessive CPU resources, leading to denial of service. The issue is fixed in version 2.9.1.

References

Community reviews

Loading reviews…