In Eclipse Mnestix AAS Generator versions 0.1.0 up until but excluding 1.5.0, a practical upper bound on the
Source GCVE Database
Not known to be exploited : upgrade to 1.5.0 soon.
Data as of 3 Nov 2026, 16:45 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 1.5.0
Exploitation evidence
Disclosed: evidence found.
CVE published 3 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 3 Nov 2026.
What to do
Upgrade Eclipse Mnestix to 1.5.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Eclipse FoundationEclipse Mnestix | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict network access to the vulnerable endpoints and monitor for abnormal request patterns involving large count values.
Description
Eclipse Mnestix AAS Generator versions 0.1.0 up to but excluding 1.5.0 do not enforce an upper limit on the client-supplied count parameter in certain API endpoints. This allows a remote unauthenticated attacker with network access to submit a large count value, causing excessive memory consumption and potential denial of service. Exploitation requires access to the ID-generation configuration from the backend repository.