mutant uncontrolled memory allocation in Forensic Parser
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
A flaw in the Forensic Parser component of aoiflux mutant lets a local user with low privileges trigger uncontrolled memory allocation by manipulating the Count argument, which can degrade the affected host. The attack must be carried out on the machine itself, and upgrading to version 2.6.0 or later resolves the issue.
Written by a model
Original description
A vulnerability was determined in aoiflux mutant 2.3.0/2.4.0/2.5.0. This vulnerability affects unknown code of the file builtin/hive_builtins.go of the component Forensic Parser. This manipulation of the argument Count causes uncontrolled memory allocation. It is possible to launch the attack on the local host. Upgrading to version 2.6.0 is able to resolve this issue. Patch name: c4b1a7dec6c603115e2a05d1e8970a142f0b9774. Upgrading the affected component is recommended.
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133406 (aoiflux mutant Forensic hive_builtins.go memory allocation), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133406 (entry last updated 2026-11-20):
Affected:
- aoiflux mutant: versions 2.3.0, 2.4.0, 2.5.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133406 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133406 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/aoiflux/mutant/pull/35
- https://github.com/aoiflux/mutant/commit/c4b1a7dec6c603115e2a05d1e8970a142f0b9774
- https://github.com/aoiflux/mutant/releases/tag/v2.6.0
- https://vuldb.com/vuln/440642
- https://vuldb.com/vuln/440642/cti
- https://vuldb.com/cve/CVE-2026-133406
- https://vuldb.com/submit/1045885
- https://github.com/aoiflux/mutant/blob/main/docs/advisories/MVF-2026-0012.md
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133406
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133406"}.Affected versions
- aoiflux mutant2.3.0, 2.4.0, 2.5.0
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.8/10CVSS 4.8
- No patch0/5No signal
What would change the score
- Would score about 60 if added to CISA KEV
- Would score about 55 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 11
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133406 |
| Record | NVD · CVE-2026-133406 |
| Other links 9 | |
| Advisory | VulDB · Advisory #440642 |
| Advisory | VulDB · Threat intelligence #440642 |
| Advisory | VulDB · CVE-2026-133406 record |
| Advisory | VulDB · Submission #1045885 |
| Advisory | GitHub · aoiflux/mutant · Advisory MVF-2026-0012.md |
| Patch | GitHub · aoiflux/mutant · Pull request #35 |
| Patch | GitHub · aoiflux/mutant · Commit c4b1a7de |
| Patch | GitHub · aoiflux/mutant · Release v2.6.0 |
| Repository | GitHub · aoiflux/mutant · Repository |
Questions about CVE-2026-133406
Is CVE-2026-133406 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133406?
mutant: versions 2.3.0, 2.4.0, 2.5.0.
Source: cve.now feed data
Related
- CVE-2026-61827netty-incubator-codec-ohttp: BinaryHttpParser should enforce limits for variable lengths fields
- CVE-2026-103025bep/imagemeta: Unbounded memory allocation decoding PNG `zTXt` "Raw profile type iptc" chunks
- CVE-2026-133234Stoatchat before 0.16.5 Memory Exhaustion via January /proxy JXL Decoding
- CVE-2026-122247Budibase: Unauthenticated global-admin & database creation via tenant-confusion bypass of the one-time init guard (`POST…
- CVE-2026-131868Convert::ASN1 versions before 0.37 for Perl allow memory exhaustion via a declared element length passed unchecked to sysread in asn_read…
- CVE-2026-118436Apache Tomcat: CGIServlet drops chunked POST body and can hang worker thread
No corrections so far. Something wrong on this page? Report an error.