mikro-orm
mikro-orm
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at mikro-orm, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-84993 | 16 Sep 2026 | mikro-orm: < 6.6.16, >= 7.0.0, < 7.1.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-44680 | 26 May 2026 | >= 7.0.0-rc.0, < 7.0.14; < 6.6.14; < 7.0.14 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-34220 | 31 Mar 2026 | < 6.6.10; >= 7.0.0-rc.0, < 7.0.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-34221 | 31 Mar 2026 | < 6.6.10; >= 7.0.0-rc.0, < 7.0.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.