[Snyk] Security upgrade org.postgresql:postgresql from 42.2.12 to 42.7.12

[snyk-io]

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

• pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Incorrect Implementation of Authentication Algorithm SNYK-JAVA-ORGPOSTGRESQL-17874248	164	org.postgresql:postgresql: 42.2.12 -> 42.7.12 No Path Found No Known Exploit

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[snyk-io]

This upgrade from version 42.2.12 to 42.7.12 is a minor version update but includes several behavioral changes and security fixes that require verification.

Key Changes:

• Behavioral Change in DatabaseMetaData: Starting with version 42.7.0, there is a notable change in how DatabaseMetaData functions operate. getCatalogs() now returns all available catalogs, and getSchemas(catalog, pattern) enforces stricter matching against the provided catalog parameter. Applications relying on the previous, less strict behavior may need adjustments. [14]
• PostgreSQL Server Version Support: As of version 42.7.4, the driver is no longer guaranteed to work with PostgreSQL server versions older than 9.1. [3, 16] It is important to verify your database server version.
• Security Fixes: This range includes multiple security patches. Notably, the target version 42.7.12 fixes a silent channel-binding authentication downgrade (CVE-2026-54291). [6, 9] Connections using channelBinding=require will now fail correctly if channel binding cannot be established, whereas they might have connected insecurely before.

Recommendation:

• Review any code that uses DatabaseMetaData.getSchemas() to ensure it is compatible with the stricter catalog matching logic.
• Confirm that your PostgreSQL server version is 9.1 or newer.
• Test database connectivity, especially if using SCRAM authentication with channelBinding=require.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.