MD5 has been replaced by SHA3.

MD5 has been replaced by SHA3.

• A. True
• B. False
• C. Only for passwords
• D. It's deprecated but still in use

Answer: (A)

MD5 is insecure because it has collision vulnerabilities, meaning two different inputs can produce the same hash. Because of that weakness, security guidance moved toward stronger hash functions, with SHA-3 (Keccak) established as the modern standard for new designs. SHA-3 offers a different structure and solid security properties that resist the kinds of attacks that undermine MD5. In the context of current practice and standards, many sources describe MD5 as replaced by SHA-3 for new implementations, which is why this statement is considered true. It’s worth noting that MD5 can still appear in legacy systems or for non-security-critical checks, but it should not be used for security-critical integrity or authentication tasks.

MD5 is insecure because it has collision vulnerabilities, meaning two different inputs can produce the same hash. Because of that weakness, security guidance moved toward stronger hash functions, with SHA-3 (Keccak) established as the modern standard for new designs. SHA-3 offers a different structure and solid security properties that resist the kinds of attacks that undermine MD5. In the context of current practice and standards, many sources describe MD5 as replaced by SHA-3 for new implementations, which is why this statement is considered true. It’s worth noting that MD5 can still appear in legacy systems or for non-security-critical checks, but it should not be used for security-critical integrity or authentication tasks.