Skip to content

Fix MySqlConnector dependency resolution in ACE.Database - #4532

Closed
KT053374 wants to merge 1 commit into
ACEmulator:masterfrom
KT053374:fix/mysqlconnector-dependency
Closed

KT053374 wants to merge 1 commit into
ACEmulator:masterfrom
KT053374:fix/mysqlconnector-dependency

Conversation

@KT053374

@KT053374 KT053374 commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

Summary

Noticed that ACE.Database was still resolving MySqlConnector 2.4.0, even though ACE.Server already references 2.6.2.

This was generating an NU1902 warning for the known vulnerability tracked under GHSA-473q-m89c-ghf8.

Problem

ACE.Database references Pomelo.EntityFrameworkCore.MySql 9.0.0 but doesn't explicitly specify a MySqlConnector version.

When restored independently, the database project resolves MySqlConnector 2.4.0, while the server project resolves 2.6.2.

Fix

Added an explicit MySqlConnector 2.6.2 reference to ACE.Database.csproj, matching the version already used by ACE.Server.

No application logic changes.

Validation

  • Confirmed that ACE.Database now resolves MySqlConnector 2.6.2.
  • Restored the projects without the previous NU1902 warnings.
  • Completed a clean Release build of ACE.Server using .NET 10.
  • Verified the change is limited to a single package reference in ACE.Database.csproj.

Impact

Keeps the MySqlConnector version consistent across the projects and prevents ACE.Database from independently restoring the vulnerable 2.4.0 version.

Since ACE.Server already references 2.6.2, this is primarily a dependency consistency and security cleanup.

@KT053374

KT053374 commented Nov 4, 2026

Copy link
Copy Markdown
Contributor Author

Apoloigies. I did not see #4531

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants