fix(deps): update dependency com.microsoft.sqlserver:mssql-jdbc to v12.6.5.jre11 [security]

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
com.microsoft.sqlserver:mssql-jdbc	12.6.0.jre11 -> 12.6.5.jre11

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

GitHub Vulnerability Alerts

CVE-2025-59250

Improper input validation in JDBC Driver for SQL Server allows an unauthorized attacker to perform spoofing over a network.

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[gemini-code-assist]

Summary of Changes

Hello @renovate-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automates the update of the Microsoft SQL Server JDBC driver to its latest patch version. The primary purpose of this update is to incorporate a critical security fix, enhancing the overall security posture of the applications using this driver by mitigating a known spoofing vulnerability.

Highlights

• Dependency Update: The com.microsoft.sqlserver:mssql-jdbc dependency has been updated from version 12.6.0.jre11 to 12.6.5.jre11.
• Security Fix: This update addresses CVE-2025-59250, a security vulnerability in the JDBC Driver for SQL Server related to improper input validation that could allow an unauthorized attacker to perform spoofing.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the com.microsoft.sqlserver:mssql-jdbc dependency from 12.6.0.jre11 to 12.6.5.jre11. This is a necessary security update to address CVE-2025-59250. The change itself is correct. I have included one suggestion to improve the project's long-term maintainability by centralizing dependency version management.

[gemini-code-assist]

While this version update is correct and necessary, I've noticed that the mssql-jdbc dependency version is hardcoded here and also in cloud-sql/sqlserver/servlet/pom.xml. To improve maintainability and prevent version drift between modules in the future, I recommend centralizing the version management.

A common practice in Maven is to define a property for the version in a parent pom.xml and reference it in child modules.

For example, in a parent pom.xml:

<properties>
  <mssql-jdbc.version>12.6.5.jre11</mssql-jdbc.version>
</properties>

Then, in this pom.xml and other modules:

<dependency>
  <groupId>com.microsoft.sqlserver</groupId>
  <artifactId>mssql-jdbc</artifactId>
  <version>${mssql-jdbc.version}</version>
</dependency>

This is likely out of scope for this automated PR, but it's a good practice to consider for easier future maintenance.