● Branch of MongoDB
MongoDB 3.4
MongoDB 3.4 reached end of life on 31 January 2020 and gets no fixes. Move to 7.0.48 or newer.
Data: .
Fix releases of MongoDB 3.4
| Release | Fixes | Signs of exploitation |
|---|---|---|
| 3.4.24 | 1 CVE record that this page reads | none among the records this page reads |
| 3.4.22 | 3 CVE records that this page reads | none among the records this page reads |
| 3.4.19 | 1 CVE record that this page reads | none among the records this page reads |
MongoDB 3.4 in dates
| What | When |
|---|---|
| Released | 30 November 2016 |
| Security fixes end | 31 January 2020 |
| Newest release | 3.4.24 (24 January 2020) |
What this page says
This page reads 200 CVE records that MongoDB's CVE Numbering Authority has published since 31 January 2020 and that name MongoDB. 8 of them are not placed on a branch. Of the others, 2 name MongoDB 3.4.
No release of MongoDB 3.4 is called safe here, because the branch has ended, whatever the records say of it.
A release is the fix of a record when the record's affected range for this branch ends before it. Dates are from the product lifecycle data credited under Sources.
Sources
- CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
- Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)