The `convert.base64-encode`, `convert.quoted-printable-encode`, and `convert.quoted-printable-decode` stream filters contain a memory handling issue. These filters use a `line-break-chars` option where the length is tracked independently of the actual string. The filter constructors use the `pestrdup()` function, which terminates the string at the first NUL byte but retains the original length. Consequently, when the filter generates a line break, it reads beyond the truncated memory allocation, resulting in the leakage of adjacent heap bytes into the filter output.