This happens when CPAN.pm detects there is a newer version of CPAN.pm living on CPAN, and then goes to install and activate the newer version. I haven't happen that to me for a long time (nowadays it seems there are no updates to CPAN.pm outside of regular perl releases), and in my experience, it first asks whether it should be upgrade. But there might be a configuration switch to do it automatically.