Questa pagina contiene un log delle modifiche di manutenzione.
Cloud SQL rilascia regolarmente aggiornamenti di manutenzione. Gli aggiornamenti di manutenzione includono nuove funzionalità, patch di sicurezza, correzioni di bug, miglioramenti delle prestazioni e altro ancora.
Gli aggiornamenti di manutenzione possono essere eseguiti da te utilizzando la manutenzione self-service o da Cloud SQL tramite aggiornamenti di manutenzione pianificati che vengono eseguiti una volta ogni qualche mese. Per gli aggiornamenti di manutenzione pianificata, puoi impostare finestre temporali per l'esecuzione degli aggiornamenti di manutenzione. Vedi Visualizzare e impostare i periodi di manutenzione.
Per scoprire di più sugli aggiornamenti della manutenzione, consulta Aggiornamenti della manutenzione sulle istanze Cloud SQL.
Per ricevere gli ultimi aggiornamenti della manutenzione, aggiungi il seguente URL al tuo
lettore di feed: https://cloud.google.com/feeds/cloud-sql-mysql-5-7-maintenance-changelog.xml.
MYSQL_5_7_44.R20251004.01_24
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| Implementazione in corso | Self-service | MySQL 5.7.44 |
Patch di sicurezza
Sistema operativo
Da aggiornare.
MYSQL_5_7_44.R20251004.01_14
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2025-11-16 | Self-service | MySQL 5.7.44 |
Patch di sicurezza
Sistema operativo
CVE-2024-56201, CVE-2024-56326, CVE-2025-11081, CVE-2025-11082, CVE-2025-11083, CVE-2025-21795, CVE-2025-27516, CVE-2025-50181
MYSQL_5_7_44.R20251004.01_07
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2025-10-20 | Manutenzione automatica | MySQL 5.7.44 |
Patch di sicurezza
Database
CVE-2025-50082, CVE-2025-50083, CVE-2025-50079, CVE-2025-50084, CVE-2025-50087, CVE-2025-50091, CVE-2025-50101, CVE-2025-50102, CVE-2025-50098, CVE-2025-53023, CVE-2025-50081, CVE-2025-50085, CVE-2025-50077, CVE-2025-50088, CVE-2025-50092, CVE-2025-50099, CVE-2025-50096, CVE-2025-21585, CVE-2025-21581, CVE-2025-30689, CVE-2025-30688, CVE-2025-30722, CVE-2025-21577, CVE-2025-21497, CVE-2025-21555, CVE-2025-21559, CVE-2025-21490, CVE-2025-21491, CVE-2025-21500, CVE-2025-21501, CVE-2025-21540, CVE-2025-21543, CVE-2025-21520, CVE-2024-21230, CVE-2024-21201, CVE-2024-21241, CVE-2024-21203, CVE-2024-21247, CVE-2024-21209, CVE-2024-21177, CVE-2024-21096, CVE-2024-21047, CVE-2024-20993, CVE-2024-20998, CVE-2024-21009, CVE-2024-21054, CVE-2024-21055, CVE-2024-21057, CVE-2024-21062, CVE-2024-21008, CVE-2024-21013, CVE-2024-20963
Sistema operativo
CVE-2015-1819, CVE-2025-38676, CVE-2025-38735, CVE-2025-39682, CVE-2025-39843, CVE-2025-6052
Altre patch
- È stato risolto il problema per cui il server, in esecuzione con autocommit=OFF, impediva il corretto funzionamento del plug-in di riscrittura delle query.
- È stato risolto il problema per cui un rollback destabilizzava l'indice virtuale quando il relativo index_id superava il valore massimo di uint32.
- È stato risolto il problema per cui le istruzioni preparate non riuscivano a compilare il tag COMMAND_CLASS nel log di controllo quando il tag NAME era Execute.
- Risolto il problema per cui il client MySQL impediva agli utenti di inviare una query contenente un simbolo di cancelletto o un doppio trattino all'interno di un commento di suggerimento dell'ottimizzatore.
- È stato risolto il problema per cui gli indici FULLTEXT di InnoDB limitavano in modo impreciso gli ID documento FTS_DOC_ID al valore massimo senza segno a 32 bit; ora il sistema supporta FTS_DOC_ID a 64 bit.
- È stato risolto il problema per cui l'eliminazione di un indice e la creazione di un indice full-text nella stessa transazione causavano l'uscita imprevista dal server.
- Risolto il problema per cui una perdita di memoria interessava il client MySQL.
- È stato risolto il problema per cui le query UNION troncavano l'output della funzione DATABASE() nelle versioni precedenti, che ora restituisce l'output corretto.
- È stato risolto il problema per cui il plug-in connection_control non riusciva a reimpostare la fase conn_delay/Waiting dopo un ritardo, il che causava dati di monitoraggio imprecisi.
- È stato risolto il problema per cui Performance Schema non riusciva a trovare chiavi specifiche nel plug-in CONNECTION_CONTROL finché non veniva eseguito il codice che le utilizzava.
- È stato risolto il problema per cui l'esecuzione simultanea di due comandi OPTIMIZE TABLE causava l'arresto imprevisto del server nelle tabelle di indice full-text quando era abilitato innodb_optimize_fulltext_only.
- È stato risolto il problema per cui un indice spaziale con una colonna SRID restituiva un risultato vuoto. Inoltre, l'utilizzo di FORCE INDEX ha causato un errore di asserzione durante l'applicazione di una scansione dell'indice di copertura su quell'indice spaziale.
- È stato risolto il problema per cui la mancanza di un controllo sul flag QT_NO_TABLE prima di accedere a table_name causava errori HEAP-USE-AFTER-FREE.
- È stato risolto il problema per cui le istruzioni preparate non aggiornavano la colonna PROCESSLIST_INFO della tabella THREADS durante l'esecuzione.
- Risolto il problema per cui un indice di colonna non valido causava un errore di asserzione InnoDB, nonostante l'indice di colonna fosse valido.
- Risolto il problema per cui il sistema doveva creare la cache binlog solo per verificare se era vuota, allocando inutilmente risorse a sessioni che non ne avevano bisogno.
- È stato risolto il problema per cui tutti i plug-in non seguivano una procedura coerente durante lo scaricamento o l'arresto; la chiamata a plugin->deinit ora comporta lo stesso comportamento per ogni plug-in.
- È stato risolto il problema per cui la gestione errata del buffer durante l'eliminazione dello spazio delle tabelle poteva causare l'interruzione del programma con un errore di asserzione.
- È stato risolto il problema per cui le operazioni simultanee causavano un errore nel sistema di ricerca full-text (FTS) nel mantenimento della coerenza.
- È stato risolto il problema per cui un'uscita imprevista del server causava la perdita delle informazioni sull'identificatore di transazione globale (GTID) persistente durante l'operazione Gtid_state::save.
- Risolto il problema per cui un elevato tasso di divisioni e unioni di pagine causava incoerenze nei dati.
MYSQL_5_7_44.R20250531.01_23
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2025-09-22 | Self-service | MySQL 5.7.44 |
Patch di sicurezza
Sistema operativo
CVE-2021-33503, CVE-2023-43804, CVE-2023-45803, CVE-2023-50782, CVE-2024-11584, CVE-2024-34397, CVE-2024-47081, CVE-2024-52533, CVE-2024-6174, CVE-2025-1153, CVE-2025-27613, CVE-2025-27614, CVE-2025-46835, CVE-2025-48384, CVE-2025-48385, CVE-2025-5244, CVE-2025-5245, CVE-2025-7545, CVE-2025-7546, CVE-2025-8224, CVE-2025-8225
MYSQL_5_7_44.R20250531.01_15
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2025-08-18 | Self-service | MySQL 5.7.44 |
Patch di sicurezza
CVE-2016-1585, CVE-2024-11053, CVE-2024-23653, CVE-2024-26130, CVE-2024-41110, CVE-2024-43840, CVE-2024-48615, CVE-2024-50349, CVE-2024-52006, CVE-2024-53427, CVE-2024-58070, CVE-2024-58083, CVE-2025-0167, CVE-2025-1181, CVE-2025-1215, CVE-2025-1365, CVE-2025-1371, CVE-2025-1372, CVE-2025-1377, CVE-2025-1632, CVE-2025-21853, CVE-2025-21867, CVE-2025-21887, CVE-2025-21962, CVE-2025-21980, CVE-2025-21997, CVE-2025-22134, CVE-2025-22870, CVE-2025-23266, CVE-2025-23267, CVE-2025-24014, CVE-2025-26603, CVE-2025-27423, CVE-2025-29087, CVE-2025-29768, CVE-2025-3198, CVE-2025-32414, CVE-2025-32415, CVE-2025-32462, CVE-2025-32463, CVE-2025-32728, CVE-2025-4598, CVE-2025-46836, CVE-2025-47273, CVE-2025-48060, CVE-2025-5914, CVE-2025-6965
MYSQL_5_7_44.R20250531.01_10
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2025-07-20 | Manutenzione automatica | MySQL 5.7.44 |
Patch di sicurezza
Non sono presenti patch di sicurezza associate a questo aggiornamento di manutenzione.
MYSQL_5_7_44.R20250304.00_03
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2025-05-12 | Self-service | MySQL 5.7.44 |
Patch di sicurezza
CVE-2022-2289, CVE-2024-57951, CVE-2024-8176, CVE-2024-9287, CVE-2025-21785, CVE-2025-21791, CVE-2025-21858, CVE-2025-21863, CVE-2025-27113
MYSQL_5_7_44.R20250304.00_01
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2025-03-26 | Manutenzione automatica | MySQL 5.7.44 |
Patch di sicurezza
CVE-2024-23653, CVE-2024-47745, CVE-2024-49861, CVE-2024-49996, CVE-2024-50047, CVE-2024-50055, CVE-2024-50067, CVE-2024-50121, CVE-2024-50164, CVE-2024-50186, CVE-2024-50275, CVE-2024-53096, CVE-2024-53099, CVE-2024-53141, CVE-2024-53142, CVE-2024-53166, CVE-2024-53168, CVE-2024-53170, CVE-2024-53173, CVE-2024-53179, CVE-2024-53206, CVE-2024-56600, CVE-2024-56601, CVE-2024-56606, CVE-2024-56614, CVE-2024-56615, CVE-2024-56635, CVE-2024-56658, CVE-2024-56664, CVE-2024-56672, CVE-2025-0840, CVE-2025-21631, CVE-2025-21652
MYSQL_5_7_44.R20241208.01_04
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2025-02-07 | Self-service | MySQL 5.7.44 |
Patch di sicurezza
CVE-2024-47682, CVE-2024-47685, CVE-2024-47696, CVE-2024-47701, CVE-2024-47727, CVE-2024-47742, CVE-2024-48957, CVE-2024-48958, CVE-2024-49860, CVE-2024-49882, CVE-2024-49883, CVE-2024-49884, CVE-2024-49889, CVE-2024-49936, CVE-2024-49967, CVE-2024-49983, CVE-2024-50033, CVE-2024-50035, CVE-2024-50036, CVE-2024-50083, CVE-2024-50115, CVE-2024-50131, CVE-2024-50143, CVE-2024-50151, CVE-2024-50154, CVE-2024-50228, CVE-2024-50257, CVE-2024-50262, CVE-2024-50264, CVE-2024-50278, CVE-2024-50279, CVE-2024-53057, CVE-2024-53082, CVE-2024-53168, CVE-2024-53179, CVE-2024-56664, CVE-2025-21631
MYSQL_5_7_44.R20241208.01_00
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2024-12-10 | Manutenzione automatica | MySQL 5.7.44 |
Patch di sicurezza
CVE-2024-0132, CVE-2024-0133, CVE-2024-46744, CVE-2024-46750, CVE-2024-46763, CVE-2024-46679, CVE-2024-46721, CVE-2024-46800, CVE-2024-46743, CVE-2024-46738, CVE-2024-43817, CVE-2024-44947, CVE-2024-45025, CVE-2024-41012, CVE-2024-45018, CVE-2024-45022, CVE-2024-45021, CVE-2024-44940, CVE-2024-46686, CVE-2007-4559, CVE-2023-27043, CVE-2024-7592, CVE-2024-6232, CVE-2024-6119, CVE-2024-45492, CVE-2024-45490, CVE-2024-45491, CVE-2024-44983, CVE-2024-43893, CVE-2024-44944, CVE-2024-43871, CVE-2024-44989, CVE-2024-44990, CVE-2024-45000, CVE-2024-42307, CVE-2024-43914, CVE-2024-43873, CVE-2024-43882, CVE-2024-44985, CVE-2024-44986, CVE-2023-7256, CVE-2024-44987, CVE-2024-43889, CVE-2024-42302, CVE-2024-41057, CVE-2024-43837, CVE-2024-43855, CVE-2024-41076, CVE-2024-42316, CVE-2024-43828, CVE-2024-43856, CVE-2024-41073, CVE-2024-44934, CVE-2024-37370, CVE-2024-37371, CVE-2023-46246, CVE-2024-41957, CVE-2024-41965, CVE-2024-41058, CVE-2024-43854, CVE-2024-43854, CVE-2024-41098, CVE-2024-42270, CVE-2023-52889, CVE-2024-42283, CVE-2024-42268, CVE-2024-42269, CVE-2024-42285, CVE-2024-6602, CVE-2024-6345, CVE-2024-2511, CVE-2024-4603, CVE-2024-4741, CVE-2024-5535, CVE-2024-7264, CVE-2024-39472, CVE-2024-6197, CVE-2024-6345, CVE-2021-36084, CVE-2021-36085, CVE-2021-36086, CVE-2021-36087, CVE-2024-39894, CVE-2024-36891
MYSQL_5_7_44.R20241020.00_00
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2024-10-25 | Self-service | MySQL 5.7.44 |
Patch di sicurezza
CVE-2024-36979, CVE-2024-37370, CVE-2024-37371, CVE-2024-37407, CVE-2024-38538, CVE-2024-38555, CVE-2024-38577, CVE-2024-39463, CVE-2024-39487, CVE-2024-40906, CVE-2024-40954, CVE-2024-40958, CVE-2024-40994, CVE-2024-41000, CVE-2024-41049, CVE-2024-41058, CVE-2024-41073, CVE-2024-41087, CVE-2024-42154, CVE-2024-42285, CVE-2024-42302, CVE-2024-43873, CVE-2024-43882, CVE-2024-44934, CVE-2024-44985, CVE-2024-44986, CVE-2024-44987, CVE-2024-45490, CVE-2024-45491, CVE-2024-45492, CVE-2024-46738, CVE-2024-46800, CVE-2024-6197, CVE-2024-6232, CVE-2024-7592
MYSQL_5_7_44.R20240915.01_02
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2024-09-17 | Manutenzione automatica | MySQL 5.7.44 |
Patch di sicurezza
Non sono presenti patch di sicurezza associate a questo aggiornamento di manutenzione.
MYSQL_5_7_44.R20240527.01_12
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2024-08-19 | Self-service | MySQL 5.7.44 |
Patch di sicurezza
CVE-2021-3520, CVE-2024-26987, CVE-2024-27013, CVE-2024-27014, CVE-2024-27015, CVE-2024-27016, CVE-2024-27018, CVE-2024-27019, CVE-2024-27020, CVE-2024-27022, CVE-2024-32002, CVE-2024-32004, CVE-2024-32020, CVE-2024-32021, CVE-2024-32465, CVE-2024-34459, CVE-2024-35195, CVE-2024-36008, CVE-2024-36901, CVE-2024-36902, CVE-2024-36938, CVE-2024-36971, CVE-2024-38428, CVE-2024-39476, CVE-2024-6387
MYSQL_5_7_44.R20240527.01_00
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2024-06-19 | Manutenzione automatica | MySQL 5.7.44 |
Patch di sicurezza
CVE-2017-18342, CVE-2022-3566, CVE-2022-3567, CVE-2023-0767, CVE-2023-22490, CVE-2023-23946, CVE-2023-25652, CVE-2023-25815, CVE-2023-29007, CVE-2023-32681, CVE-2023-42465, CVE-2023-4641, CVE-2023-48231, CVE-2023-48232, CVE-2023-48233, CVE-2023-48234, CVE-2023-48235, CVE-2023-48236, CVE-2023-48237, CVE-2023-48706, CVE-2023-50387, CVE-2023-50868, CVE-2023-52425, CVE-2023-52426, CVE-2023-52429, CVE-2023-52434, CVE-2023-52435, CVE-2023-52620, CVE-2023-52752, CVE-2023-52772, CVE-2023-5388, CVE-2023-6135, CVE-2023-6237, CVE-2023-7008, CVE-2024-0743, CVE-2024-2004, CVE-2024-22667, CVE-2024-23307, CVE-2024-2379, CVE-2024-23851, CVE-2024-2398, CVE-2024-2466, CVE-2024-25629, CVE-2024-26584, CVE-2024-26585, CVE-2024-26601, CVE-2024-26602, CVE-2024-26603, CVE-2024-26643, CVE-2024-26808, CVE-2024-26809, CVE-2024-26882, CVE-2024-26883, CVE-2024-26884, CVE-2024-26885, CVE-2024-26900, CVE-2024-26901, CVE-2024-26907, CVE-2024-26908, CVE-2024-26910, CVE-2024-28182, CVE-2024-28757, CVE-2024-3772
MYSQL_5_7_44.R20240207.00_12
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2024-05-07 | Self-service | MySQL 5.7.44 |
Patch di sicurezza
CVE-2022-3566, CVE-2022-3567, CVE-2023-48231, CVE-2023-48232, CVE-2023-48233, CVE-2023-48234, CVE-2023-48235, CVE-2023-48236, CVE-2023-48237, CVE-2023-48706, CVE-2023-52429, CVE-2023-52434, CVE-2023-52435, CVE-2023-6237, CVE-2024-22667, CVE-2024-23851, CVE-2024-26585
MYSQL_5_7_44.R20240207.00_10
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2024-03-25 | Self-service | MySQL 5.7.44 |
Patch di sicurezza
CVE-2023-40546, CVE-2023-40547, CVE-2023-40548, CVE-2023-40549, CVE-2023-40550, CVE-2023-40551, CVE-2023-46838, CVE-2023-49083, CVE-2023-52439, CVE-2023-52443, CVE-2023-52447, CVE-2023-6129, CVE-2024-0607, CVE-2024-0684, CVE-2024-0727, CVE-2024-0853, CVE-2024-1085, CVE-2024-1086, CVE-2024-24557, CVE-2024-25062, CVE-2024-26589, CVE-2024-26591
MYSQL_5_7_44.R20240207.00_07
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2024-02-26 | Manutenzione automatica | MySQL 5.7.44 |
Patch di sicurezza
CVE-2022-42010, CVE-2022-42011, CVE-2022-42012, CVE-2023-1077, CVE-2023-2156, CVE-2023-28938, CVE-2023-31022, CVE-2023-34324, CVE-2023-34969, CVE-2023-35945, CVE-2023-38545, CVE-2023-39189, CVE-2023-39192, CVE-2023-39194, CVE-2023-39325, CVE-2023-42754, CVE-2023-42756, CVE-2023-44487, CVE-2023-45322, CVE-2023-45863, CVE-2023-46218, CVE-2023-46219, CVE-2023-46813, CVE-2023-4733, CVE-2023-4734, CVE-2023-4735, CVE-2023-4736, CVE-2023-4738, CVE-2023-4750, CVE-2023-4752, CVE-2023-4781, CVE-2023-48795, CVE-2023-51384, CVE-2023-51385, CVE-2023-52071, CVE-2023-5344, CVE-2023-5441, CVE-2023-5535, CVE-2023-5717, CVE-2023-6111, CVE-2023-6531, CVE-2023-6817, CVE-2023-6915, CVE-2023-6931, CVE-2023-6932, CVE-2023-7104, CVE-2023-7192, CVE-2024-0193, CVE-2024-0553, CVE-2024-0565, CVE-2024-0567, CVE-2024-0584, CVE-2024-0646, CVE-2024-0775, CVE-2024-22195
MYSQL_5_7_44.R20231105.01_00
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2023-11-23 | Manutenzione automatica | MySQL 5.7.44 |
Patch di sicurezza
CVE-2020-22916, CVE-2022-47008, CVE-2022-47010, CVE-2022-48063, CVE-2022-48065, CVE-2023-23914, CVE-2023-28938, CVE-2023-29499, CVE-2023-32611, CVE-2023-32665, CVE-2023-3338, CVE-2023-38039, CVE-2023-38545, CVE-2023-39192, CVE-2023-39194, CVE-2023-4016, CVE-2023-42754, CVE-2023-42756, CVE-2023-45863, CVE-2023-4622, CVE-2018-1121, CVE-2022-4269, CVE-2022-47007, CVE-2022-47011, CVE-2022-48064, CVE-2023-28736, CVE-2023-32636, CVE-2023-32643, CVE-2023-39189, CVE-2023-4128, CVE-2023-4206, CVE-2023-4207, CVE-2023-4208, CVE-2023-42753, CVE-2023-4623, CVE-2023-4921
MYSQL_5_7_43.R20230909.02_00
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2023-09-15 | Manutenzione automatica | MySQL 5.7.43 |
Patch di sicurezza
CVE-2015-8863, CVE-2016-4074, CVE-2018-17075, CVE-2018-17142, CVE-2018-17143, CVE-2018-17846, CVE-2018-17847, CVE-2018-17848, CVE-2022-28737, CVE-2022-3623, CVE-2023-0160, CVE-2023-1206, CVE-2023-2269, CVE-2023-2860, CVE-2023-29491, CVE-2023-3090, CVE-2023-31248, CVE-2023-32001, CVE-2023-3389, CVE-2023-35001, CVE-2023-3567, CVE-2023-3609, CVE-2023-3611, CVE-2023-3776, CVE-2023-3777, CVE-2023-3812, CVE-2023-3817, CVE-2023-38408, CVE-2023-4004, CVE-2023-4147, CVE-2023-4194, CVE-2023-4387, CVE-2023-4459
MYSQL_5_7_42.R20230530.03_11
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2023-08-04 | Self-service | MySQL 5.7.42 |
Patch di sicurezza
CVE-2022-1796, CVE-2022-26365, CVE-2022-27652, CVE-2022-33740, CVE-2022-33741, CVE-2022-33742, CVE-2022-36109, CVE-2022-36879, CVE-2022-42703, CVE-2022-4744, CVE-2023-0394, CVE-2023-0459, CVE-2023-1295, CVE-2023-1786, CVE-2023-1972, CVE-2023-2248, CVE-2023-23916, CVE-2023-2426, CVE-2023-2609, CVE-2023-2610, CVE-2023-27534, CVE-2023-28484, CVE-2023-28842, CVE-2023-29469, CVE-2023-3006, CVE-2023-3268
MYSQL_5_7_40.R20230314.03_06
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2023-06-07 | Self-service | MySQL 5.7.40 |
Patch di sicurezza
CVE-2022-4292, CVE-2022-4141, CVE-2021-41089, CVE-2020-14040, CVE-2023-0433, CVE-2023-0512, CVE-2023-0288, CVE-2023-23931, CVE-2023-0051, CVE-2023-1998, CVE-2023-1127, CVE-2023-1170, CVE-2020-28852, CVE-2022-1158, CVE-2023-1175, CVE-2022-1886, CVE-2021-41091, CVE-2023-27561, CVE-2023-28466, CVE-2023-0049, CVE-2023-0054, CVE-2023-0466, CVE-2023-2513, CVE-2023-1872, CVE-2023-28642, CVE-2023-0464, CVE-2023-1252, CVE-2023-1582, CVE-2023-1264, CVE-2023-0465, CVE-2023-25809, CVE-2023-1355, CVE-2023-28327, CVE-2023-0045, CVE-2023-2162, CVE-2023-0458
MYSQL_5_7_40.R20230314.03_02
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2023-04-26 | Manutenzione automatica | MySQL 5.7.40 |
Patch di sicurezza
CVE-2022-23471, CVE-2022-35260, CVE-2022-32221, CVE-2022-4696, CVE-2023-1252, CVE-2023-1637, CVE-2023-28772, CVE-2023-23454, CVE-2023-1249, CVE-2021-43618, CVE-2022-40897, CVE-2022-32149, CVE-2023-26604, CVE-2022-47946, CVE-2023-0215, CVE-2022-4378, CVE-2022-4450, CVE-2022-4285, CVE-2022-27239, CVE-2022-42328, CVE-2023-0286, CVE-2023-23586, CVE-2022-48303, CVE-2019-9924, CVE-2023-0461, CVE-2023-25153, CVE-2021-38561, CVE-2022-29869, CVE-2023-25173, CVE-2022-47929, CVE-2021-20208, CVE-2023-0590, CVE-2022-46663, CVE-2022-42329, CVE-2019-18276, CVE-2022-4304, CVE-2022-29154, CVE-2022-0563, CVE-2022-42432
MYSQL_5_7_39.R20221108.00_02
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2022-12-08 | Self-service | MySQL 5.7.39 |
Patch di sicurezza
CVE-2022-2289, CVE-2022-2208, CVE-2022-2287, CVE-2022-2862, CVE-2022-2923, CVE-2022-3278, CVE-2022-35252, CVE-2022-3234, CVE-2022-3297, CVE-2022-2905, CVE-2022-3352, CVE-2022-2817, CVE-2022-42915, CVE-2022-3705, CVE-2022-2344, CVE-2022-3235, CVE-2022-2580, CVE-2022-3586, CVE-2022-3028, CVE-2022-41222, CVE-2022-2598, CVE-2022-2183, CVE-2022-1508, CVE-2022-2602, CVE-2022-2343, CVE-2022-3324, CVE-2022-2345, CVE-2022-2980, CVE-2021-3669, CVE-2022-3256, CVE-2022-2175, CVE-2022-1271, CVE-2022-2231, CVE-2022-39188, CVE-2022-2819, CVE-2021-46848, CVE-2022-3296, CVE-2022-2284, CVE-2022-3524, CVE-2022-2874, CVE-2022-2207, CVE-2022-3153, CVE-2022-2182, CVE-2022-20409, CVE-2022-2286, CVE-2022-2816
MYSQL_5_7_38.R20220809.02_02
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2022-09-20 | Self-service | MySQL 5.7.38 |
Patch di sicurezza
CVE-2022-2097, CVE-2022-21505, CVE-2022-2959, CVE-2021-4159, CVE-2022-0168, CVE-2022-35737, CVE-2022-2503, CVE-2022-2938, CVE-2022-33744, CVE-2022-29154, CVE-2022-36123, CVE-2022-0850
Addendum Patch di sicurezza
MYSQL_5_7_37.R20220508.01_09
| Data di uscita | Tipo di release | Versione secondaria del database | |
|---|---|---|---|
| 2022-08-08 | Self-service | MySQL 5.7.37 |
Patch di sicurezza
CVE-2022-0854, CVE-2022-1154, CVE-2022-1160, CVE-2022-1353, CVE-2022-1381, CVE-2022-1420, CVE-2022-1616, CVE-2022-1619, CVE-2022-1620, CVE-2022-1621, CVE-2022-1629, CVE-2022-1674, CVE-2022-1720, CVE-2022-1733, CVE-2022-1735, CVE-2022-1769, CVE-2022-1771, CVE-2022-1785, CVE-2022-1851, CVE-2022-1898, CVE-2022-1927, CVE-2022-1942, CVE-2022-2124, CVE-2022-2125, CVE-2022-2126, CVE-2022-2129, CVE-2022-22576, CVE-2022-2327, CVE-2022-27774, CVE-2022-27775, CVE-2022-27776, CVE-2022-27778, CVE-2022-27779, CVE-2022-27780, CVE-2022-27781, CVE-2022-27782, CVE-2022-30115, CVE-2022-32205, CVE-2022-32206, CVE-2022-32207, CVE-2022-32208, CVE-2022-33743, CVE-2021-33656
Addendum Patch di sicurezza
MYSQL_5_7_37.R20220508.01_08
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2022-07-26 | Self-service | MySQL 5.7.37 |
Patch di sicurezza
CVE-2022-0995, CVE-2021-26341, CVE-2021-4203, CVE-2022-29217, CVE-2022-29162, CVE-2022-2068, CVE-2022-1998, CVE-2022-1011, CVE-2022-31030, CVE-2022-1292, CVE-2021-22600
MYSQL_5_7_37.R20220508.01_03
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2022-06-20 | Self-service | MySQL 5.7.37 |
Patch di sicurezza
CVE-2022-0494, CVE-2022-1116, CVE-2022-1516, CVE-2022-1786, CVE-2022-1729, CVE-2022-29458, CVE-2022-29581, CVE-2022-28893, CVE-2022-30594
MYSQL_5_7_36.R20220220.01_15
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2022-05-09 | Self-service | MySQL 5.7.36 |
Patch di sicurezza
CVE-2020-13529, CVE-2020-36516, CVE-2021-20321, CVE-2021-3732, CVE-2021-3753, CVE-2021-4154, CVE-2021-45346, CVE-2022-0001, CVE-2022-0002, CVE-2022-0264, CVE-2022-0617, CVE-2022-0847, CVE-2022-0886, CVE-2022-0943, CVE-2022-1055, CVE-2022-23308, CVE-2022-23648, CVE-2022-24448, CVE-2022-24769, CVE-2022-27666, CVE-2022-29582
Addendum Patch di sicurezza
MYSQL_5_7_36.R20220220.01_13
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2022-04-22 | Self-service | MySQL 5.7.36 |
Patch di sicurezza
CVE-2021-3743, CVE-2021-4001, CVE-2021-22570, CVE-2021-28714, CVE-2021-28715, CVE-2021-34556, CVE-2021-35477, CVE-2022-0778,
MYSQL_5_7_36.R20220220.01_08
| Data di uscita | Tipo di release | Versione secondaria del database |
|---|---|---|
| 2022-03-31 | Self-service | MySQL 5.7.36 |
Patch di sicurezza
CVE-2020-12403, CVE-2021-3711, CVE-2021-3770, CVE-2021-3778, CVE-2021-3796, CVE-2021-3872, CVE-2021-3875, CVE-2021-3903, CVE-2021-3927, CVE-2021-3928, CVE-2021-3968, CVE-2021-3973, CVE-2021-3974, CVE-2021-3984, CVE-2021-4002, CVE-2021-4019, CVE-2021-4069, CVE-2021-4083, CVE-2021-4136, CVE-2021-4166, CVE-2021-4173, CVE-2021-4187, CVE-2021-4192, CVE-2021-4193, CVE-2021-20322, CVE-2021-22945, CVE-2021-32760, CVE-2021-39537, CVE-2021-40528, CVE-2021-41103, CVE-2021-41190, CVE-2021-43527, CVE-2021-43784, CVE-2021-43816, CVE-2022-0128, CVE-2022-0156, CVE-2022-0158, CVE-2022-0185, CVE-2022-0261, CVE-2022-0318, CVE-2022-0319, CVE-2022-0359, CVE-2022-0361, CVE-2022-0368, CVE-2022-0392, CVE-2022-0393, CVE-2022-0407, CVE-2022-0408, CVE-2022-0413, CVE-2022-0443, CVE-2022-0492