Back to changelog
February 20, 2025
We've improved our Maven CVE resolution by addressing a class of false positives that could occur when CVEs listed multiple packages across different ecosystems.
🔍 What's Fixed?
Previously, packages like com.microsoft.azure:msal4j@1.15.1
could incorrectly match vulnerabilities intended for other ecosystems (e.g., @azure/identity@<4.2.1
from npm). Now, our platform accurately filters vulnerabilities by both ecosystem and package name, ensuring only relevant CVEs are flagged.
This update enhances accuracy in your vulnerability alerts, giving you greater confidence in your security insights.