Neoengine maintains a narrowly scoped product portfolio centered on its core engine offering, with a small disclosures footprint that reflects limited public visibility or a nascent disclosure history. The observed vulnerabilities are classified under general categories that do not yet reveal a durable pattern of specific weakness classes; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Neoengine over time
Signals from CVEs in this vendor scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2006-6226HIGH Multiple format string vulnerabilities in NeoEngine 0.8.2 and earlier, and CVS 3422, allow remote attackers to cause a denial of service and possibly execute arbitrary code via (1) | Dec 2, 2006 | 7.5 | 20 | NO | NO |
CVE-2006-6227MEDIUM The Core::Receive function in neonet/core.cpp for NeoEngine 0.8.2 and earlier, and CVS 3422, allow remote attackers to cause a denial of service (engine crash) via a message with a | Dec 2, 2006 | 5.0 | 15 | NO | NO |
Signals from CVEs in this vendor scope (2 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Neoengine.
Media articles that mention a CVE ID that affects a product developed by Neoengine — matched by CVE ID, not by vendor name.