We use exact versions here to make sure that attempts to launch unit tests from Maven will use configuration at least similar to the main configuration.

PgJDBC isn't included into distribution of H2 and H2 doesn't depend on it, so neither we nor users of H2 are affected by security issues in libraries used only in our unit tests, alerts about them can be ignored.

Please, try latest 42.7.2 instead of this old 42.5.*, it will be more reasonable to upgrade to some modern version.

Thank you for the feedback, I have adopted 42.7.2 as advised.

PgJDBC isn't included into distribution of H2 and H2 doesn't depend on it, so neither we nor users of H2 are affected by security issues in libraries used only in our unit tests, alerts about them can be ignored.

From what I can see, the Maven build file (which is not effective) is defining the dependency and so any security scanner will think that H2 was affected by this vulnerability. Unfortunately even a wrong security report is still a report and that's why I have tried to fix it.