Fix CVE-2025-55163

[brfrn169]

Description

This PR fixes CVE-2025-55163 by bumping up the Cosmos DB library to 4.75.0.

Related issues and/or PRs

N/A

Changes made

• Bumped up the Cosmos DB library to 4.75.0.

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes.
• I have considered whether similar issues could occur in other products, components, or modules if this PR is for bug fixes.
• Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
• Tests (unit, integration, etc.) have been added for the changes.
• My changes generate no new warnings.
• Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

N/A

Release notes

Upgraded the Cosmos DB library to fix a security issue. CVE-2025-55163

[gemini-code-assist]

Summary of Changes

Hello @brfrn169, 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 focuses on enhancing the security posture of the application by resolving a critical vulnerability, CVE-2025-55163. This is accomplished through a targeted update of the Azure Cosmos DB library to a more secure version, ensuring protection against known exploits associated with the older dependency.

Highlights

• Security Fix: This pull request addresses and fixes the security vulnerability identified as CVE-2025-55163.
• Dependency Update: The resolution for the CVE is achieved by upgrading the Azure Cosmos DB library.
• Version Bump: The azureCosmosVersion in the build.gradle file has been updated from 4.71.0 to 4.75.0.

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. ↩

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[gemini-code-assist]

Code Review

This pull request updates the Cosmos DB library to version 4.75.0 to fix a security vulnerability. The change itself in build.gradle is correct. However, I have added a high-severity comment to emphasize the importance of running regression tests to ensure this dependency upgrade does not introduce any breaking changes, as the PR checklist suggests this step might have been overlooked.

[Torch3333]

LGTM, thank you!

[komamitsu]

LGTM, thank you!