Skip to main content
VulnerabilityPublished Updated

CVE-2026-104874: Reference leak in CIMultiDict/MultiDict items-view union and subtraction

Affects scoutsuiteSource GCVE Database

0
Compare
Authoritative record:CVE-2026-104874· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 5.14.0_17 when convenient.

Data as of 1 Nov 2026, 00:22 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 5.14.0_17
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 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 31 Oct 2026.

What to do

Upgrade scoutsuite to 5.14.0_17.

Affected software

ProductAffectedFixed in
Homebrewscoutsuitepkg:brew/scoutsuiteOther threatsAffected
  • >=5.14.0_13 <5.14.0_17
Fixed in
  • 5.14.0_17

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied to upgrade to version 5.14.0_17 or later of the affected product. Applying the official fix will prevent the reference leak and associated memory exhaustion. No other mitigation actions are indicated or required.

Description

A reference leak vulnerability exists in the items-view union and subtraction operators of aio-libs/multidict versions 6.7.0 through 6.9.0. This flaw allows a remote client to cause unbounded memory growth by leaking references to key-identity and value objects during certain set operations on items views. The leak occurs because the code fails to release new references created during parsing, leading to unreclaimable memory consumption until the process is terminated.

References

Community reviews

Loading reviews…