[3.13] gh-145264: Do not ignore excess Base64 data after the first padded quad (GH-145267) (GH-146326)#146348

Merged

ambv merged 1 commit intopython:3.13from

miss-islington:backport-e31c551-3.13

Mar 23, 2026

Merged

[3.13] gh-145264: Do not ignore excess Base64 data after the first padded quad (GH-145267) (GH-146326)#146348
ambv merged 1 commit intopython:3.13from
miss-islington:backport-e31c551-3.13

Conversation

Copy link

Contributor

miss-islington commentedMar 23, 2026•
edited by bedevere-appbot
Loading

Base64 decoder (see binascii.a2b_base64(), base64.b64decode(), etc)
no longer ignores excess data after the first padded quad in non-strict
(default) mode. Instead, in conformance with RFC 4648, it ignores the
pad character, "=", if it is present before the end of the encoded data.
(cherry picked from commit4561f64)
(cherry picked from commite31c551)

Co-authored-by: Serhiy Storchakastorchaka@gmail.com

Issue:Excess Base64 data ignored after padding by default #145264

[3.14]pythongh-145264: Do not ignore excess Base64 data after the fi…

bd4ab52

…rst padded quad (pythonGH-145267) (pythonGH-146326)Base64 decoder (see binascii.a2b_base64(), base64.b64decode(), etc)no longer ignores excess data after the first padded quad in non-strict(default) mode.  Instead, in conformance with RFC 4648, it ignores thepad character, "=", if it is present before the end of the encoded data.(cherry picked from commit4561f64)(cherry picked from commite31c551)Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>

This was referencedMar 23, 2026

Excess Base64 data ignored after padding by default#145264

Closed

[3.14] gh-145264: Do not ignore excess Base64 data after the first padded quad (GH-145267)#146326

Merged