Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

Python

Pythonвысокоуровневый язык программирования общего назначения. Его философия дизайна делает акцент на читаемости кода.

Релизный цикл, информация об уязвимостях

Продукт: Python
Вендор: python

График релизов

3.103.113.123.133.1420212022202320242025202620272028202920302031

Релизные элементы

KBВерсияБилдДата доступности
3.13.153.13.15
3.13.143.13.14
3.13.133.13.13
3.13.123.13.12
3.13.113.13.11
3.13.103.13.10
3.13.93.13.9
3.13.83.13.8
3.13.73.13.7
3.13.63.13.6

Показывать по

Недавние уязвимости Python

Количество 1 113

rocky логотип

RLSA-2026:2419

8 месяцев назад

Moderate: python3.12 security update

EPSS: Низкий
oracle-oval логотип

ELSA-2026-2419

8 месяцев назад

ELSA-2026-2419: python3.12 security update (MODERATE)

EPSS: Низкий
oracle-oval логотип

ELSA-2026-1537

8 месяцев назад

ELSA-2026-1537: python security update (MODERATE)

EPSS: Низкий
rocky логотип

RLSA-2026:1478

8 месяцев назад

Moderate: python3.9 security update

EPSS: Низкий
oracle-oval логотип

ELSA-2026-1631

8 месяцев назад

ELSA-2026-1631: python3 security update (MODERATE)

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2026:0337-1

8 месяцев назад

Security update for python

EPSS: Низкий
oracle-oval логотип

ELSA-2026-1478

8 месяцев назад

ELSA-2026-1478: python3.9 security update (MODERATE)

EPSS: Низкий
nvd логотип

CVE-2025-12781

8 месяцев назад

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
EPSS: Низкий
redhat логотип

CVE-2025-12781

8 месяцев назад

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
EPSS: Низкий
debian логотип

CVE-2025-12781

8 месяцев назад

When passing data to the b64decode(), standard_b64decode(), and urlsaf ...

CVSS3: 5.3
EPSS: Низкий

Уязвимостей на страницу

Уязвимость
CVSS
EPSS
Опубликовано
1
rocky логотип
RLSA-2026:2419

Moderate: python3.12 security update

2%
Низкий
8 месяцев назад
oracle-oval логотип
ELSA-2026-2419

ELSA-2026-2419: python3.12 security update (MODERATE)

2%
Низкий
8 месяцев назад
oracle-oval логотип
ELSA-2026-1537

ELSA-2026-1537: python security update (MODERATE)

1%
Низкий
8 месяцев назад
rocky логотип
RLSA-2026:1478

Moderate: python3.9 security update

1%
Низкий
8 месяцев назад
oracle-oval логотип
ELSA-2026-1631

ELSA-2026-1631: python3 security update (MODERATE)

1%
Низкий
8 месяцев назад
suse-cvrf логотип
SUSE-SU-2026:0337-1

Security update for python

0%
Низкий
8 месяцев назад
oracle-oval логотип
ELSA-2026-1478

ELSA-2026-1478: python3.9 security update (MODERATE)

1%
Низкий
8 месяцев назад
nvd логотип
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 месяцев назад
redhat логотип
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 месяцев назад
debian логотип
CVE-2025-12781

When passing data to the b64decode(), standard_b64decode(), and urlsaf ...

CVSS3: 5.3
1%
Низкий
8 месяцев назад

Уязвимостей на страницу


Поделиться