You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
mb_decode_mimeheader does not handle separator #20674
if encoded Subject are too long they need to be separated the block by space ?= =? or line break, but mb_decode_mimeheader does not handle it correctly
An 'encoded-word' may not be more than 75 characters long, including
'charset', 'encoding', 'encoded-text', and delimiters. If it is
desirable to encode more text than will fit in an 'encoded-word' of
75 characters, multiple 'encoded-word's (separated by CRLF SPACE) may
be used.
Should be separated by CRLF SPACE if 'encoded-word' is more than 75 characters.
Activity
iluuu1994 commentedon Dec 9, 2025
/cc @alexdowad
Fix phpGH-20674 mb_decode_mimeheader does not handle separator
youkidearitai commentedon Dec 10, 2025
I create a commit this fix issue: youkidearitai@d29c866. @alexdowad what do you think?
youkidearitai commentedon Dec 10, 2025
In RFC2047
Should be separated by CRLF SPACE if 'encoded-word' is more than 75 characters.
Fix GH-20674 mb_decode_mimeheader does not handle separator
Fix phpGH-20674 mb_decode_mimeheader does not handle separator