Skip to main content
VulnerabilityPublished

CVE-2026-133406: aoiflux mutant · Uncontrolled Memory Allocation

Affects aoiflux mutantSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.8 Medium · fixed in 2.6.0 : update aoiflux mutant when convenient.

Data as of 20 Nov 2026, 00:39 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulDB)CVSS 4.04.8
CNA (VulDB)CVSS 3.13.3
CNA (VulDB)CVSS 3.03.3
CNA (VulDB)CVSS 2.01.7
Patch
Available – fixed in 2.6.0
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 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 19 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
aoifluxmutantAffected
  • =2.3.0
  • =2.4.0
  • =2.5.0
Fixed in–
Gogithub.com/aoiflux/mutantpkg:golang/github.com/aoiflux/mutantOther threatsAffected
  • =2.3.0
  • =2.4.0
  • =2.5.0
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:aoiflux:mutant:*:*:*:*:*:*:*:*

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

AI-suggested

Upgrade aoiflux mutant to version 2.6.0 or later, which contains the official fix for this vulnerability. No additional mitigations are indicated by the vendor advisory.

Description

CVE-2026-133406 is a medium severity vulnerability in aoiflux mutant versions 2.3.0, 2.4.0, and 2.5.0. It involves uncontrolled memory allocation caused by manipulation of the Count argument in the Forensic Parser component, specifically in the builtin/hive_builtins.go file. The vulnerability can be exploited locally. Upgrading to version 2.6.0 resolves the issue.

References

Community reviews

Loading reviews…