Understanding software encryption

[xOAT]

I was wondering if you guys can help me understand software encryption. I know software encryption can require updates as vulnerabilities are discovered, but don't understand how that actually fixes the problem. Consider the scenario, I have a software encrypted file via VeraCrypt. I get hacked and the file is stolen. Why cant the attacker install an older version of VeraCrypt and use the known vulnerabilities to get access? Does the updated version modify the encrypted files so that they are re-secured?

[Peter Vaughan Truslow]

I was wondering if you guys can help me understand software encryption. I know software encryption can require updates as vulnerabilities are discovered, but don't understand how that actually fixes the problem. Consider the scenario, I have a software encrypted file via VeraCrypt. I get hacked and the file is stolen. Why cant the attacker install an older version of VeraCrypt and use the known vulnerabilities to get access? Does the updated version modify the encrypted files so that they are re-secured?

I'm not an encryption expert, but if it's using standardized encryption algorithms, then the vulnerabilities are probably within the software itself, such as a way of a hacker getting access to the private key. if it is an update to the algorithm itself, then although I can't say if it re-encrypts the files as I haven't dealt with much encryption, I can say that if I was writing a encryption program, I'd make it re-encrypt whenever the algorithm was updated.

maybe this is a good question for the people who work for VeraCrypt, as they could more accurately answer this question than my semi-educated guess.

edit: also if they have patch notes, that would be a good place to find information like this.