The function verifyInclusionKeccak is not used anywhere but its in the scope of this audit. There is no validation that proof is a tree and a valid tree like it described in the comments. E.x. if proof is less than 32 length, that function will just return a leaf without reverting. In my opinion, function doesnt work as expected and can be exploited. Ive submitted the same issue with processInclusionProofSha256 function that lead to loss a funds for validator due the same issue.
src/contracts/libraries/Merkle.sol#L49
I think its important to add security to that function like this:
Sidu28 (EigenLayer) confirmed
Alex the Entreprenerd (judge) decreased severity to QA and commented:
