Skip to content

[Snyk] Security upgrade MimeKit from 2.11.0 to 4.15.1 #161

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ashmuck wants to merge 2 commits into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade MimeKit from 2.11.0 to 4.15.1 #161

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
70d2795
fix: IndicoV2/IndicoV2.csproj to reduce vulnerabilities
snyk-bot Mar 12, 2026
32a2d8e
fix: IndicoV2/IndicoV2.csproj to reduce vulnerabilities
snyk-bot Mar 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion IndicoV2/IndicoV2.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@
<PackageReference Include="GraphQL.Client.Serializer.Newtonsoft" Version="3.2.3" />
<PackageReference Include="GraphQL.Client" Version="3.2.3" />
<PackageReference Include="Newtonsoft.Json" Version="13.0.3" />
<PackageReference Include="MimeKit" Version="2.11.0" />
<PackageReference Include="MimeKit" Version="4.15.1" />
Copy link
Copy Markdown

@cursor cursor bot Mar 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Security upgrade incomplete: test project still references vulnerable version

Medium Severity

The MimeKit upgrade to 4.15.1 was only applied in IndicoV2/IndicoV2.csproj, but IndicoV2.IntegrationTests/IndicoV2.IntegrationTests.csproj still explicitly references the vulnerable MimeKit version 2.11.0. Before this change, both projects referenced the same version; now they're inconsistent. While NuGet resolution may pick the higher transitive version at build time, the explicit vulnerable reference remains and Snyk will likely continue flagging it.

Fix in Cursor Fix in Web

<PackageReference Include="StrawberryShake.Transport.Http" Version="12.2.2" />
</ItemGroup>

Expand Down
Loading