Python — высокоуровневый язык программирования общего назначения. Его философия дизайна делает акцент на читаемости кода.
Релизный цикл, информация об уязвимостях
График релизов
Релизные элементы
| KB | Версия | Билд | Дата доступности |
|---|---|---|---|
| 3.13.15 | 3.13.15 | ||
| 3.13.14 | 3.13.14 | ||
| 3.13.13 | 3.13.13 | ||
| 3.13.12 | 3.13.12 | ||
| 3.13.11 | 3.13.11 | ||
| 3.13.10 | 3.13.10 | ||
| 3.13.9 | 3.13.9 | ||
| 3.13.8 | 3.13.8 | ||
| 3.13.7 | 3.13.7 | ||
| 3.13.6 | 3.13.6 |
Показывать по
Количество 1 113
RLSA-2026:2419
Moderate: python3.12 security update
ELSA-2026-2419
ELSA-2026-2419: python3.12 security update (MODERATE)
ELSA-2026-1537
ELSA-2026-1537: python security update (MODERATE)
RLSA-2026:1478
Moderate: python3.9 security update
ELSA-2026-1631
ELSA-2026-1631: python3 security update (MODERATE)
SUSE-SU-2026:0337-1
Security update for python
ELSA-2026-1478
ELSA-2026-1478: python3.9 security update (MODERATE)
CVE-2025-12781
When passing data to the b64decode(), standard_b64decode(), and urlsafe_b64decode() functions in the "base64" module the characters "+/" will always be accepted, regardless of the value of "altchars" parameter, typically used to establish an "alternative base64 alphabet" such as the URL safe alphabet. This behavior matches what is recommended in earlier base64 RFCs, but newer RFCs now recommend either dropping characters outside the specified base64 alphabet or raising an error. The old behavior has the possibility of causing data integrity issues. This behavior can only be insecure if your application uses an alternate base64 alphabet (without "+/"). If your application does not use the "altchars" parameter or the urlsafe_b64decode() function, then your application does not use an alternative base64 alphabet. The attached patches DOES NOT make the base64-decode behavior raise an error, as this would be a change in behavior and break existing programs. Instead, the patch deprec
CVE-2025-12781
When passing data to the b64decode(), standard_b64decode(), and urlsafe_b64decode() functions in the "base64" module the characters "+/" will always be accepted, regardless of the value of "altchars" parameter, typically used to establish an "alternative base64 alphabet" such as the URL safe alphabet. This behavior matches what is recommended in earlier base64 RFCs, but newer RFCs now recommend either dropping characters outside the specified base64 alphabet or raising an error. The old behavior has the possibility of causing data integrity issues. This behavior can only be insecure if your application uses an alternate base64 alphabet (without "+/"). If your application does not use the "altchars" parameter or the urlsafe_b64decode() function, then your application does not use an alternative base64 alphabet. The attached patches DOES NOT make the base64-decode behavior raise an error, as this would be a change in behavior and break existing programs. Instead, the patch deprecates ...
CVE-2025-12781
When passing data to the b64decode(), standard_b64decode(), and urlsaf ...
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано 1 | |
|---|---|---|---|---|
RLSA-2026:2419 Moderate: python3.12 security update | 2% Низкий | 8 месяцев назад | ||
ELSA-2026-2419 ELSA-2026-2419: python3.12 security update (MODERATE) | 2% Низкий | 8 месяцев назад | ||
ELSA-2026-1537 ELSA-2026-1537: python security update (MODERATE) | 1% Низкий | 8 месяцев назад | ||
RLSA-2026:1478 Moderate: python3.9 security update | 1% Низкий | 8 месяцев назад | ||
ELSA-2026-1631 ELSA-2026-1631: python3 security update (MODERATE) | 1% Низкий | 8 месяцев назад | ||
SUSE-SU-2026:0337-1 Security update for python | 0% Низкий | 8 месяцев назад | ||
ELSA-2026-1478 ELSA-2026-1478: python3.9 security update (MODERATE) | 1% Низкий | 8 месяцев назад | ||
CVE-2025-12781 When passing data to the b64decode(), standard_b64decode(), and urlsafe_b64decode() functions in the "base64" module the characters "+/" will always be accepted, regardless of the value of "altchars" parameter, typically used to establish an "alternative base64 alphabet" such as the URL safe alphabet. This behavior matches what is recommended in earlier base64 RFCs, but newer RFCs now recommend either dropping characters outside the specified base64 alphabet or raising an error. The old behavior has the possibility of causing data integrity issues. This behavior can only be insecure if your application uses an alternate base64 alphabet (without "+/"). If your application does not use the "altchars" parameter or the urlsafe_b64decode() function, then your application does not use an alternative base64 alphabet. The attached patches DOES NOT make the base64-decode behavior raise an error, as this would be a change in behavior and break existing programs. Instead, the patch deprec | CVSS3: 5.3 | 1% Низкий | 8 месяцев назад | |
CVE-2025-12781 When passing data to the b64decode(), standard_b64decode(), and urlsafe_b64decode() functions in the "base64" module the characters "+/" will always be accepted, regardless of the value of "altchars" parameter, typically used to establish an "alternative base64 alphabet" such as the URL safe alphabet. This behavior matches what is recommended in earlier base64 RFCs, but newer RFCs now recommend either dropping characters outside the specified base64 alphabet or raising an error. The old behavior has the possibility of causing data integrity issues. This behavior can only be insecure if your application uses an alternate base64 alphabet (without "+/"). If your application does not use the "altchars" parameter or the urlsafe_b64decode() function, then your application does not use an alternative base64 alphabet. The attached patches DOES NOT make the base64-decode behavior raise an error, as this would be a change in behavior and break existing programs. Instead, the patch deprecates ... | CVSS3: 5.3 | 1% Низкий | 8 месяцев назад | |
CVE-2025-12781 When passing data to the b64decode(), standard_b64decode(), and urlsaf ... | CVSS3: 5.3 | 1% Низкий | 8 месяцев назад |
Уязвимостей на страницу