Why does bash's tab completion trigger the stack protector?

I’m using bash 5.0.16 (and bash-completion 2.10) on Manjaro. Today, I absentmindedly hit the tab key while moving some files, and was greeted with an unexpected message:

[charles@wirepile some_dir]$ mv ~down*** stack smashing detected ***: <unknown> terminated

I had to ^C to regain control of the shell.

It appears that my (up-to-date Manjaro) build of bash triggers the stack protector whenever tab completion is invoked on the tilde character, with or without other characters following it. The following does work:

[charles@wirepile some_dir]$ ls ~/
.this_dir/                .that_file                 another_file

I shouldn’t have any unusual lines in my .bashrc, unless Manjaro customizes it by default.

I imagine this is some sort of buffer overrun and should be considered a bug — is it somehow intentional? Should I contact the developers, or the package maintainers?

I’m also curious — can anyone reproduce this issue?