THANK YOU!!!
Note that this stale certificate may also be in the "System" keychain (NOT System Roots) and cause this problem.
The root cause of this is a screw-up by Verisign/Symantec a decade ago, creating “VeriSign Class 3 Public Primary Certification Authority - G5” as an intermediate certificate signed by a weaker (1024-bit) root certificate. They "fixed" that error by re-issuing “VeriSign Class 3 Public Primary Certification Authority - G5” as a self-signed root with the same common name, distinguished name, and public key. That way they didn't need to re-issue all their customers' certificates signed with the intermediate. However, the removal of the stale weak root that had signed the original intermediate version from System Roots in El Capitan left the intermediate version as rootless, and it is actually indeterminate whether the system will pick the new root or the old broken intermediate when verifying a signature chain because all of the supposedly unique identifiers are the same. In principle the intermediate (in the login or System keychain) should be used but in testing chain verification in Keychain Access on a machine with both certs I found that sometimes a downstream cert used one path and sometimes it used the other. No theory why...