Skip to content

chore(deps): update nuget packages#1159

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/nuget
Open

chore(deps): update nuget packages#1159
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/nuget

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Feb 17, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
AMQPNetLite.Core 2.5.12.5.2 age confidence
AWSSDK.Core 3.7.500.803.7.501 age confidence
AWSSDK.S3 3.7.510.63.7.511.7 age confidence
AWSSDK.SQS 3.7.502.393.7.502.56 age confidence
AWSSDK.SecurityToken 3.7.504.323.7.504.49 age confidence
Destructurama.Attributed (source) 5.2.05.3.0 age confidence
Google.Cloud.PubSub.V1 3.32.03.34.0 age confidence
Grpc.AspNetCore.Web 2.76.02.80.0 age confidence
Grpc.Core.Api 2.76.02.80.0 age confidence
Grpc.HealthCheck 2.76.02.80.0 age confidence
Grpc.Net.Client 2.76.02.80.0 age confidence
Grpc.Net.Common 2.76.02.80.0 age confidence
Microsoft.AspNetCore.TestHost (source) 8.0.248.0.27 age confidence
Microsoft.Bcl.AsyncInterfaces (source) 10.0.310.0.8 age confidence
Microsoft.Extensions.Caching.Memory (source) 10.0.310.0.8 age confidence
Microsoft.Extensions.Configuration (source) 10.0.310.0.8 age confidence
Microsoft.Extensions.Configuration.Binder (source) 10.0.310.0.8 age confidence
Microsoft.Extensions.Configuration.CommandLine (source) 10.0.310.0.8 age confidence
Microsoft.Extensions.Configuration.EnvironmentVariables (source) 10.0.310.0.8 age confidence
Microsoft.Extensions.Configuration.Json (source) 10.0.310.0.8 age confidence
Microsoft.Extensions.DependencyInjection (source) 10.0.310.0.8 age confidence
Microsoft.Extensions.DependencyInjection.Abstractions (source) 10.0.310.0.8 age confidence
Microsoft.Extensions.Diagnostics.HealthChecks (source) 8.0.248.0.27 age confidence
Microsoft.Extensions.Logging.Abstractions (source) 10.0.310.0.8 age confidence
Microsoft.NET.Test.Sdk 18.0.118.5.1 age confidence
NATS.Client.JetStream 2.7.22.8.0 age confidence
NATS.Net 2.7.22.8.0 age confidence
NUnit (source) 4.4.04.6.0 age confidence
NUnit.Analyzers 4.11.24.13.0 age confidence
NUnit3TestAdapter (source) 6.1.06.2.0 age confidence
StackExchange.Redis (source) 2.11.02.13.1 age confidence
coverlet.collector 8.0.08.0.1 age confidence

Warning

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


Release Notes

Azure/amqpnetlite (AMQPNetLite.Core)

v2.5.2: Release 2.5.2

Fixes and improvements:

  • [#​630] Add OnLinkStateProperties callback for flow link-state properties
  • [#​634] Handle ObjectDisposedException in WebSocket close
aws/aws-sdk-net (AWSSDK.S3)

v3.7.511

destructurama/attributed (Destructurama.Attributed)

v5.3.0

Compare Source

New features

  • Add UsingAttributes overload used by serilog-settings-configuration by @​sungam3r in #​230

Changes for CI and tests

Full Changelog: destructurama/attributed@5.2.0...5.3.0

googleapis/google-cloud-dotnet (Google.Cloud.PubSub.V1)

v3.34.0: Google.Cloud.PubSub.V1 version 3.34.0

Compare Source

Bug fixes
  • Increase streaming pull timeout
Documentation improvements
  • Fix documentation URL AIInference MessageTransform service_account_email field

v3.33.0: Google.Cloud.PubSub.V1 version 3.33.0

Compare Source

New features
  • Add BigtableConfig type
grpc/grpc-dotnet (Grpc.AspNetCore.Web)

v2.80.0

What's Changed
New Contributors

Full Changelog: grpc/grpc-dotnet@v2.76.0...v2.80.0

dotnet/dotnet (Microsoft.Bcl.AsyncInterfaces)

v10.0.8

v10.0.7

v10.0.6

v10.0.5

v10.0.4

microsoft/vstest (Microsoft.NET.Test.Sdk)

v18.5.1

What's Changed

Full Changelog: microsoft/vstest@v18.5.0...v18.5.1

v18.5.0

⚠️ Unlisted on Nuget, because of #​15718

What's Changed

Full Changelog: microsoft/vstest@v18.4.0...v18.5.0

v18.4.0

What's Changed
New Contributors

Full Changelog: microsoft/vstest@v18.3.0...v18.4.0

v18.3.0

What's Changed
Internal fixes and updates
New Contributors
nats-io/nats.net (NATS.Client.JetStream)

v2.8.0: NATS .NET v2.8.0

NuGet

Happy to announce the NATS .NET 2.8.0 stable release of the 2.8 line. It picks up the NATS Server v2.14 client surface (consumer reset, $JS.FC.* flow-control replies, Consumer field on stream source/mirror, AllowBatchPublish on stream config), ships two breaking changes that landed in the preview cycle, and fixes in-flight message loss on consumer/connection dispose behind an opt-in drain.

A big thank you to all NATS contributors and community members who helped make this release possible. <3

NATS Server v2.14 Features

  • ResetConsumerAsync on INatsJSContext and INatsJSConsumer (ADR-60), to reset a pinned consumer's state (#​1126).
  • $JS.FC.* flow-control replies are parsed by the JS metadata layer, for streams that publish with the js_ack_fc_v2 flag (#​1127).
  • Consumer field on StreamSource and stream mirror config, for pre-created mirror/source consumers (#​1128).
  • AllowBatchPublish on StreamConfig (JSON allow_batched), required by streams that opt into fast-ingest batch publishing per ADR-50 (#​1120). The fast-ingest publisher itself lives in orbit.net alongside the existing atomic batch publisher.

Breaking Changes

Subject Validation On By Default (#​1093)

Subjects containing whitespace (space, tab, CR, LF) now throw NatsException. This closes a class of CRLF injection issues from malformed subjects.

Opt out if you rely on legacy subjects that contain whitespace:

var opts = NatsOpts.Default with { SkipSubjectValidation = true };
NKeyPair Removed From NATS.Client.Core (#​1101)

NATS.Client.Core.NKeys and NKeyPair are removed. Signing now goes through the NATS.NKeys package, which lets the nkey/Ed25519 code be versioned independently of the client.

For typical users this is transparent: keep using NatsAuthOpts.NKeyFile, CredsFile, Jwt + Seed, or AuthCredCallback and the client wires up the new signer automatically.

Only direct callers of NATS.Client.Core.NKeyPair need to switch:

// Before
using NATS.Client.Core;
var kp = NKeyPair.FromSeed(seed);
var sig = kp.Sign(nonce);

// After
using NATS.NKeys;
var kp = KeyPair.FromSeed(seed);
var sig = kp.Sign(nonce);

Other Notable Changes

  • Server error event (#​745): a new event on NatsConnection surfaces server-side errors to client code.
  • Message loss on consumer dispose (#​1085): opt-in drain keeps in-flight messages from being dropped when a consumer or connection is disposed. Enable with:
    var opts = NatsOpts.Default with
    {
        DrainSubscriptionsOnDispose = true,
        ConsumerDrainOnDisposeTimeout = TimeSpan.FromSeconds(10),
    };
  • Auth signs the server nonce regardless of auth_required advertisement (#​1109), so NKey/credential clients respond to the challenge even when the server doesn't advertise auth_required.
  • Connection state resets cleanly on credential loading failure (#​1107).
  • Duplicate status headers no longer leak an incorrect Pin ID (#​1116); other Pin ID handling improvements (#​1099).
  • KV watcher cancellation behavior fix (#​1084).
  • Protocol size checks: 64MB incoming payload cap, matching nats.js (#​1095).
  • Range attribute fix on MaxBytes (#​1096).
  • ArrayPool buffers are cleared before return to pool (#​1097).

What's Changed

Since 2.8.0-preview.3:

  • Add server error event (#​745)
  • Add Client and Orbit section to README (#​1133)
  • Add Example Docs (#​1119)
  • Migrate solution to slnx format (#​1131)

2.8.0-preview.3:

  • Fix message loss on consumer dispose (#​1085)
  • Add consumer reset API (#​1126) [server 2.14]
  • Add consumer field on stream source/mirror (#​1128) [server 2.14]
  • Add $JS.FC support to JS metadata parser (#​1127) [server 2.14]

2.8.0-preview.2:

  • Add AllowBatchPublish stream config field (#​1120) [server 2.14]
  • Bump OpenTelemetry and OpenTelemetry.Exporter.OpenTelemetryProtocol (#​1121)
  • Fix setting wrong pin id from status header (#​1116) (thanks @​colprog)
  • Fix slow-consumer test first-ping RTT flap (#​1115)
  • Fix net481 TLS test flakes (#​1111)
  • Rewrite README intro (#​1114)

2.8.0-preview.1:

Full Changelog: nats-io/nats.net@v2.7.3...v2.8.0

Download from NuGet at https://www.nuget.org/packages/NATS.Net/2.8.0

v2.7.3: NATS .NET v2.7.3

Announcing a new version of NATS .NET client library covering various fixes and a security update on one dependency for NETStandard targets (#​1089) even though the vulnerable API is not used by our library.

A big thank you to all NATS contributors and community members who helped make this release possible ❤️

Breaking Changes
NakAsync Signature Change (#​1081)

The TimeSpan delay parameter has been removed from INatsJSMsg<T>.NakAsync(). The delay must now be passed via AckOpts.NakDelay.

Before (v2.7.2):

await msg.NakAsync(delay: TimeSpan.FromSeconds(5));
await msg.NakAsync(opts, TimeSpan.FromSeconds(5));

After (v2.7.3):

// Option 1: Use the new extension method
await msg.NakAsync(TimeSpan.FromSeconds(5));

// Option 2: Use AckOpts with NakDelay
await msg.NakAsync(new AckOpts { NakDelay = TimeSpan.FromSeconds(5) });

Note: because we also have an extension method, recompiling your project is enough.

AckTerminateAsync TermWithReason (#​1048, #​1081)

AckTerminateAsync now supports an optional termination reason. A new overload and a new TerminateReason property on AckOpts have been added to INatsJSMsg<T>. Implementors of this interface must add the new method.

// New overload
await msg.AckTerminateAsync("processing failed permanently");

// Or via AckOpts
await msg.AckTerminateAsync(new AckOpts { TerminateReason = "processing failed permanently" });

// Extension method shorthand
await msg.AckTerminateAsync("reason", cancellationToken);

Requires NATS Server 2.10.4+.

PinnedClient Validation (#​1063)

Calling NextAsync(), FetchAsync(), or FetchNoWaitAsync() on a consumer with PriorityPolicy.PinnedClient now throws NatsJSException. Use ConsumeAsync() instead.

// This now throws NatsJSException:
var msg = await consumer.NextAsync<string>();

// Use ConsumeAsync instead:
await foreach (var msg in consumer.ConsumeAsync<string>())
{
    // process message
}
Consumer Cancellation Handling (#​1068)

Consumer methods (ConsumeAsync, FetchAsync, NextAsync) now call cancellationToken.ThrowIfCancellationRequested() immediately at method entry. Previously cancelled tokens were checked later in the async pipeline.

var cts = new CancellationTokenSource();
cts.Cancel();

// v2.7.2: exception thrown sometime during async operation
// v2.7.3: OperationCanceledException thrown immediately
await consumer.FetchAsync<string>(cancellationToken: cts.Token);
StreamSnapshotRequest ChunkSize Type Change (#​1088)

StreamSnapshotRequest.ChunkSize changed from long to int? with a narrower validation range (1KB–1MB). WindowSize (int?) was added as a new optional property.

// Before (v2.7.2)
var req = new StreamSnapshotRequest { ChunkSize = 1024L };

// After (v2.7.3)
var req = new StreamSnapshotRequest
{
    ChunkSize = 1024,          // int? now, valid range: 1024–1048576
    WindowSize = 8388608,      // new optional, valid range: 1024–33554432
};

WindowSize requires NATS Server 2.12.5+.

OpenTelemetry Tag Change (#​1078)

The telemetry tag network.protocol.version (value: protocol version number) has been replaced with network.transport (value: "tcp") to align with OpenTelemetry semantic conventions. Update any dashboards or alerting rules that filter on the old tag name.

Default Parameter Values Changed from default to null (#​1081)

All optional parameters on INatsJSMsg<T> methods (AckAsync, NakAsync, AckProgressAsync, AckTerminateAsync, ReplyAsync) changed from = default to = null. This is source-compatible but binary-breaking — existing compiled assemblies must be recompiled against v2.7.3.

What's Changed

Full Changelog: nats-io/nats.net@v2.7.2...v2.7.3

CVE Update

Microsoft.Bcl.Memory is a transitive dependency for netstandard2.0 targets any app pulling in NATS.Client.Core gets it. Even though this library doesn't call the vulnerable Base64Url.Decode API, the consuming application (or another dependency in its graph) might. A CVSSv3 7.5 DoS from a malformed network input is not something you want sitting in your dependency tree. (Microsoft CVE )

If you are not upgrading to this new version of NATS .NET AND targeting NETStandard2.0, applications should add an explicit package reference to force the patched version:

  <PackageReference Include="Microsoft.Bcl.Memory" Version="9.0.14" />

You don't need to upgrade NATS.NET itself to get the fix if you need time. NuGet will happily resolve the newer patch version of Microsoft.Bcl.Memory since it's within the same major.minor range.

Here is a report generated by AI:

NAT .NET library implementation is not affected by the same bug. Different vulnerability, different code.

The CVE is about an out-of-bounds read in System.Buffers.Text.Base64Url's decode path when processing malformed
input — that's a SIMD-optimized native implementation with pointer arithmetic that can overrun its buffer.

Your custom Base64UrlEncoder (borrowed from Azure AD IdentityModel):

  • Decode path: Converts Base64Url chars back to standard Base64 chars (- → +, _ → /), pads with =, then delegates to
    Convert.FromBase64String(). The actual decoding is done by the framework's well-tested Convert.FromBase64String,
    which will throw FormatException on malformed input rather than reading out of bounds.
  • Validates input length: Rejects length % 4 == 1 upfront (line 164), which is always invalid.
  • Bounded loops: The unsafe code in UnsafeDecode only iterates up to str.Length and decodedLength (which is at most
    str.Length + 3), and the output string is allocated to exactly decodedLength.

The implementation is sound. It's not pretty (mutating "immutable" strings via fixed pointers is a hack), but it's
not vulnerable to the same class of bug.

Download from NuGet at https://www.nuget.org/packages/NATS.Net/2.7.3

nunit/nunit (NUnit)

v4.6.0: NUnit 4.6.0

Compare Source

See release notes for details.

v4.5.1: V 4.5.1

Compare Source

See release notes for details.

v4.5.0: V 4.5.0

Compare Source

See release notes for details.

nunit/nunit.analyzers (NUnit.Analyzers)

v4.13.0: NUnit Analyzers 4.13 - May 2, 2026

Compare Source

NUnit Analyzers 4.13 - May 2, 2026

This release of the NUnit Analyzers updates analyzer handling for the NUnit 4.6 API change that replaces
ActualValueDelegate<> with Func<> - see nunit/nunit#4824 for more information.
Analyzers now also consider the return type of Func<> in assertions. The release also includes one bug fix and
some dependency updates.

The release contains contributions from the following users (in alphabetical order):

Issues Resolved

Features and Enhancements

  • #​982 Recognized Func<T> return values

Bugs

  • #​968 Whitespace issue in Does.Contain fixer when assert spans multiple lines

Tooling, Process, and Documentation

  • #​985 chore: Bump year to 2026 in copyrights
  • #​978 Bump cake.tool from 6.0.0 to 6.1.0
  • #​976 chore: Correct documentation
  • #​975 chore: bump version
  • #​956 Bump cake.tool from 4.0.0 to 6.0.0

v4.12.0: NUnit Analyzers 4.12 - March 3, 2026

Compare Source

NUnit Analyzers 4.12 - March 3, 2026

This release of the NUnit Analyzers improves NUnit1029 to account for TestCaseSource
support for params and optional arguments. It also introduces a new analyzer for incorrect
usage of Is.Not.Null.Or.Empty, fixes regressions in NUnit2005 and NUnit2055, and updates
NUnit package dependencies.

The release contains contributions from the following users (in alphabetical order):

Issues Resolved

Features and Enhancements

  • #​957 Relax NUnit1029 for TestCaseSource where method accepts a single "params" array
  • #​189 Warning when Is.Not.Null.Or.Empty used

Bugs

  • #​953 Code fix for NUnit2055 can generate invalid code for classic asserts
  • #​952 Code fix for NUnit2005 tries to use Is.Empty constraint on incompatible types.

Tooling, Process, and Documentation

  • #​973 chore: Bump NUnit version
  • #​970 chore: Bump NUnit to version 4.5.0
  • #​967 Fix note about works with Unity Test Framework
  • #​937 chore: bump version
nunit/nunit3-vs-adapter (NUnit3TestAdapter)

v6.2.0: V 6.2.0

See release notes

StackExchange/StackExchange.Redis (StackExchange.Redis)

v2.13.1

Compare Source

IMPORTANT: This release changes the default protocol from RESP2 to RESP3 for Azure Managed Redis endpoints (only); this
has scalability and feature advantages, but if you are using modules or ad-hoc commands, please see the RESP3 notes, which includes:

  • the purpose of RESP3
  • scenarios where RESP2 vs RESP3 may be visible
  • how to explicitly choose to remain on RESP2
  • notes on additional libraries such as NRedisStack

What's Changed

Full Changelog: StackExchange/StackExchange.Redis@2.12.27...2.13.1

v2.12.14

Compare Source

What's Changed

Impact: "high" if using cluster and high-integrity-mode together (resolves an issue that can mis-report -MOVED responses as integrity failures)

NuGet link

New Contributors

Full Changelog: StackExchange/StackExchange.Redis@2.12.8...2.12.14

v2.12.8

Compare Source

What's Changed

  • Filter out 'temporary place

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@renovate renovate Bot changed the title chore(deps): update dependency awssdk.core to 3.7.500.81 chore(deps): update nuget packages Feb 17, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Feb 17, 2026

🔍 Vulnerabilities of dockerhubaneo/armonik_core_stream_test_client:0.38.3-renovatenuget.1.sha.3478a052

📦 Image Reference dockerhubaneo/armonik_core_stream_test_client:0.38.3-renovatenuget.1.sha.3478a052
digestsha256:457076377a096137d7ff14e98bff9dd6bb07fcdcfbca01d1c4132eb98ae7e172
vulnerabilitiescritical: 0 high: 0 medium: 12 low: 3
platformlinux/amd64
size337 MB
packages1126
📦 Base Image ubuntu:24.04
also known as
  • 84bda043709f9066841484e9b8e440aa0d6d04ab49d09e367ef0fb68ace864cf
  • latest
  • noble
  • noble-20260410
digestsha256:cdb5fd928fced577cfecf12c8966e830fcdf42ee481fb0b91904eeddc2fe5eff
vulnerabilitiescritical: 0 high: 0 medium: 9 low: 2
critical: 0 high: 0 medium: 3 low: 0 libc6 2.39-0ubuntu8.7 (deb)

pkg:deb/ubuntu/libc6@2.39-0ubuntu8.7?arch=amd64&distro=ubuntu-24.04&upstream=glibc

# Dockerfile (3:10)
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS base-linux
USER $APP_UID
ENTRYPOINT [ "dotnet" ]

FROM mcr.microsoft.com/dotnet/sdk:10.0-nanoserver-ltsc2022 AS base-windows
ENTRYPOINT ["C:\\Program Files\\dotnet\\dotnet.exe"]

FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:10.0 AS build-linux

medium : CVE--2026--4438

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.045%
EPSS Percentile14th percentile
Description

Calling gethostbyaddr or gethostbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend in the GNU C library version 2.34 to version 2.43 could result in an invalid DNS hostname being returned to the caller in violation of the DNS specification.

medium : CVE--2026--4437

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.068%
EPSS Percentile21st percentile
Description

Calling gethostbyaddr or gethostbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend in the GNU C Library version 2.34 to version 2.43 could, with a crafted response from the configured DNS server, result in a violation of the DNS specification that causes the application to treat a non-answer section of the DNS response as a valid answer.

medium : CVE--2026--4046

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.065%
EPSS Percentile20th percentile
Description

The iconv() function in the GNU C Library versions 2.43 and earlier may crash due to an assertion failure when converting inputs from the IBM1390 or IBM1399 character sets, which may be used to remotely crash an application. This vulnerability can be trivially mitigated by removing the IBM1390 and IBM1399 character sets from systems that do not need them.

critical: 0 high: 0 medium: 2 low: 0 tar 1.35+dfsg-3build1 (deb)

pkg:deb/ubuntu/tar@1.35%2Bdfsg-3build1?arch=amd64&distro=ubuntu-24.04

# Dockerfile (3:10)
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS base-linux
USER $APP_UID
ENTRYPOINT [ "dotnet" ]

FROM mcr.microsoft.com/dotnet/sdk:10.0-nanoserver-ltsc2022 AS base-windows
ENTRYPOINT ["C:\\Program Files\\dotnet\\dotnet.exe"]

FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:10.0 AS build-linux

medium 5.5: CVE--2026--5704

Affected range>=0
Fixed versionNot Fixed
CVSS Score5.5
CVSS VectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS Score0.032%
EPSS Percentile10th percentile
Description

A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection.

medium : CVE--2025--45582

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.130%
EPSS Percentile32nd percentile
Description

GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each "tar xf" in its Security Rules of Thumb; however, third-party advice leads users to run "tar xf" more than once into the same directory.

critical: 0 high: 0 medium: 1 low: 0 libcap2 1:2.66-5ubuntu2.2 (deb)

pkg:deb/ubuntu/libcap2@1%3A2.66-5ubuntu2.2?arch=amd64&distro=ubuntu-24.04

# Dockerfile (3:10)
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS base-linux
USER $APP_UID
ENTRYPOINT [ "dotnet" ]

FROM mcr.microsoft.com/dotnet/sdk:10.0-nanoserver-ltsc2022 AS base-windows
ENTRYPOINT ["C:\\Program Files\\dotnet\\dotnet.exe"]

FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:10.0 AS build-linux

medium 7.0: CVE--2026--4878

Affected range<1:2.66-5ubuntu2.4
Fixed version1:2.66-5ubuntu2.4
CVSS Score7
CVSS VectorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score0.010%
EPSS Percentile1st percentile
Description

A flaw was found in libcap. A local unprivileged user can exploit a Time-of-check-to-time-of-use (TOCTOU) race condition in the cap_set_file() function. This allows an attacker with write access to a parent directory to redirect file capability updates to an attacker-controlled file. By doing so, capabilities can be injected into or stripped from unintended executables, leading to privilege escalation.

critical: 0 high: 0 medium: 1 low: 0 dpkg 1.22.6ubuntu6.5 (deb)

pkg:deb/ubuntu/dpkg@1.22.6ubuntu6.5?arch=amd64&distro=ubuntu-24.04

# Dockerfile (3:10)
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS base-linux
USER $APP_UID
ENTRYPOINT [ "dotnet" ]

FROM mcr.microsoft.com/dotnet/sdk:10.0-nanoserver-ltsc2022 AS base-windows
ENTRYPOINT ["C:\\Program Files\\dotnet\\dotnet.exe"]

FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:10.0 AS build-linux

medium : CVE--2026--2219

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.020%
EPSS Percentile5th percentile
Description

It was discovered that dpkg-deb (a component of dpkg, the Debian package management system) does not properly validate the end of the data stream when uncompressing a zstd-compressed .deb archive, which may result in denial of service (infinite loop spinning the CPU).

critical: 0 high: 0 medium: 1 low: 0 util-linux 2.39.3-9ubuntu6.5 (deb)

pkg:deb/ubuntu/util-linux@2.39.3-9ubuntu6.5?arch=amd64&distro=ubuntu-24.04

# Dockerfile (3:10)
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS base-linux
USER $APP_UID
ENTRYPOINT [ "dotnet" ]

FROM mcr.microsoft.com/dotnet/sdk:10.0-nanoserver-ltsc2022 AS base-windows
ENTRYPOINT ["C:\\Program Files\\dotnet\\dotnet.exe"]

FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:10.0 AS build-linux

medium : CVE--2026--27456

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.017%
EPSS Percentile4th percentile
Description

util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.

critical: 0 high: 0 medium: 1 low: 0 git 1:2.43.0-1ubuntu7.3 (deb)

pkg:deb/ubuntu/git@1%3A2.43.0-1ubuntu7.3?arch=amd64&distro=ubuntu-24.04

# Dockerfile (3:10)
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS base-linux
USER $APP_UID
ENTRYPOINT [ "dotnet" ]

FROM mcr.microsoft.com/dotnet/sdk:10.0-nanoserver-ltsc2022 AS base-windows
ENTRYPOINT ["C:\\Program Files\\dotnet\\dotnet.exe"]

FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:10.0 AS build-linux

medium 8.8: CVE--2024--52005

Affected range>=0
Fixed versionNot Fixed
CVSS Score8.8
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score0.384%
EPSS Percentile60th percentile
Description

Git is a source code management tool. When cloning from a server (or fetching, or pushing), informational or error messages are transported from the remote Git process to the client via the so-called "sideband channel". These messages will be prefixed with "remote:" and printed directly to the standard error output. Typically, this standard error output is connected to a terminal that understands ANSI escape sequences, which Git did not protect against. Most modern terminals support control sequences that can be used by a malicious actor to hide and misrepresent information, or to mislead the user into executing untrusted scripts. As requested on the git-security mailing list, the patches are under discussion on the public mailing list. Users are advised to update as soon as possible. Users unable to upgrade should avoid recursive clones unless they are from trusted sources.

critical: 0 high: 0 medium: 1 low: 0 libexpat1 2.6.1-2ubuntu0.4 (deb)

pkg:deb/ubuntu/libexpat1@2.6.1-2ubuntu0.4?arch=amd64&distro=ubuntu-24.04&upstream=expat

# Dockerfile (3:10)
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS base-linux
USER $APP_UID
ENTRYPOINT [ "dotnet" ]

FROM mcr.microsoft.com/dotnet/sdk:10.0-nanoserver-ltsc2022 AS base-windows
ENTRYPOINT ["C:\\Program Files\\dotnet\\dotnet.exe"]

FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:10.0 AS build-linux

medium 5.5: CVE--2025--66382

Affected range>=0
Fixed versionNot Fixed
CVSS Score5.5
CVSS VectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS Score0.008%
EPSS Percentile1st percentile
Description

In libexpat through 2.7.3, a crafted file with an approximate size of 2 MiB can lead to dozens of seconds of processing time.

critical: 0 high: 0 medium: 1 low: 0 wget 1.21.4-1ubuntu4.1 (deb)

pkg:deb/ubuntu/wget@1.21.4-1ubuntu4.1?arch=amd64&distro=ubuntu-24.04

# Dockerfile (3:10)
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS base-linux
USER $APP_UID
ENTRYPOINT [ "dotnet" ]

FROM mcr.microsoft.com/dotnet/sdk:10.0-nanoserver-ltsc2022 AS base-windows
ENTRYPOINT ["C:\\Program Files\\dotnet\\dotnet.exe"]

FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:10.0 AS build-linux

medium 6.1: CVE--2021--31879

Affected range>=0
Fixed versionNot Fixed
CVSS Score6.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
EPSS Score0.154%
EPSS Percentile36th percentile
Description

GNU Wget through 1.21.1 does not omit the Authorization header upon a redirect to a different origin, a related issue to CVE-2018-1000007.

critical: 0 high: 0 medium: 1 low: 0 sed 4.9-2build1 (deb)

pkg:deb/ubuntu/sed@4.9-2build1?arch=amd64&distro=ubuntu-24.04

# Dockerfile (3:10)
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS base-linux
USER $APP_UID
ENTRYPOINT [ "dotnet" ]

FROM mcr.microsoft.com/dotnet/sdk:10.0-nanoserver-ltsc2022 AS base-windows
ENTRYPOINT ["C:\\Program Files\\dotnet\\dotnet.exe"]

FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:10.0 AS build-linux

medium : CVE--2026--5958

Affected range<4.9-2ubuntu0.24.04.1
Fixed version4.9-2ubuntu0.24.04.1
EPSS Score0.005%
EPSS Percentile0th percentile
Description

When sed is invoked with both -i (in-place edit) and --follow-symlinks, the function open_next_file() performs two separate, non-atomic filesystem operations on the same path: 1. resolves symlink to its target and stores the resolved path for determining when output is written, 2. opens the original symlink path (not the resolved one) to read the file. Between these two calls there is a race window. If an attacker atomically replaces the symlink with a different target during that window, sed will: read content from the new (attacker-chosen) symlink target and write the processed result to the path recorded in step 1. This can lead to arbitrary file overwrite with attacker-controlled content in the context of the sed process. This issue was fixed in version 4.10.

critical: 0 high: 0 medium: 0 low: 1 libgcrypt20 1.10.3-2build1 (deb)

pkg:deb/ubuntu/libgcrypt20@1.10.3-2build1?arch=amd64&distro=ubuntu-24.04

# Dockerfile (3:10)
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS base-linux
USER $APP_UID
ENTRYPOINT [ "dotnet" ]

FROM mcr.microsoft.com/dotnet/sdk:10.0-nanoserver-ltsc2022 AS base-windows
ENTRYPOINT ["C:\\Program Files\\dotnet\\dotnet.exe"]

FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:10.0 AS build-linux

low : CVE--2024--2236

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.666%
EPSS Percentile71st percentile
Description

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

critical: 0 high: 0 medium: 0 low: 1 libicu74 74.2-1ubuntu3.1 (deb)

pkg:deb/ubuntu/libicu74@74.2-1ubuntu3.1?arch=amd64&distro=ubuntu-24.04&upstream=icu

# Dockerfile (3:10)
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS base-linux
USER $APP_UID
ENTRYPOINT [ "dotnet" ]

FROM mcr.microsoft.com/dotnet/sdk:10.0-nanoserver-ltsc2022 AS base-windows
ENTRYPOINT ["C:\\Program Files\\dotnet\\dotnet.exe"]

FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:10.0 AS build-linux

low : CVE--2025--5222

Affected range>=0
Fixed versionNot Fixed
EPSS Score0.033%
EPSS Percentile10th percentile
Description

A stack buffer overflow was found in Internationl components for unicode (ICU ). While running the genrb binary, the 'subtag' struct overflowed at the SRBRoot::addTag function. This issue may lead to memory corruption and local arbitrary code execution.

critical: 0 high: 0 medium: 0 low: 1 passwd 1:4.13+dfsg1-4ubuntu3.2 (deb)

pkg:deb/ubuntu/passwd@1%3A4.13%2Bdfsg1-4ubuntu3.2?arch=amd64&distro=ubuntu-24.04&upstream=shadow

# Dockerfile (3:10)
FROM mcr.microsoft.com/dotnet/sdk:10.0 AS base-linux
USER $APP_UID
ENTRYPOINT [ "dotnet" ]

FROM mcr.microsoft.com/dotnet/sdk:10.0-nanoserver-ltsc2022 AS base-windows
ENTRYPOINT ["C:\\Program Files\\dotnet\\dotnet.exe"]

FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:10.0 AS build-linux

low : CVE--2024--56433

Affected range>=0
Fixed versionNot Fixed
EPSS Score4.509%
EPSS Percentile89th percentile
Description

shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.

@renovate renovate Bot force-pushed the renovate/nuget branch 9 times, most recently from 8e8cd80 to cee7be5 Compare February 24, 2026 14:20
@renovate renovate Bot force-pushed the renovate/nuget branch 3 times, most recently from fdf5317 to 07fe229 Compare March 4, 2026 02:40
@renovate renovate Bot force-pushed the renovate/nuget branch 10 times, most recently from 24e770f to ead2e06 Compare March 13, 2026 01:19
@renovate renovate Bot force-pushed the renovate/nuget branch 5 times, most recently from 3e693dd to 1b44aee Compare March 17, 2026 13:23
@renovate renovate Bot force-pushed the renovate/nuget branch 4 times, most recently from 4aa2ee7 to 4e137c0 Compare March 27, 2026 09:22
@renovate renovate Bot force-pushed the renovate/nuget branch 3 times, most recently from d31bcfb to 270504f Compare April 8, 2026 20:40
@renovate renovate Bot force-pushed the renovate/nuget branch 4 times, most recently from c97abd1 to 77da2ab Compare April 16, 2026 10:53
@renovate renovate Bot force-pushed the renovate/nuget branch 8 times, most recently from ca6570c to 1b506eb Compare April 28, 2026 08:45
@renovate renovate Bot force-pushed the renovate/nuget branch 5 times, most recently from 645cb7f to c401812 Compare May 5, 2026 01:14
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented May 5, 2026

@renovate renovate Bot force-pushed the renovate/nuget branch 2 times, most recently from 4a03b7e to 0de7511 Compare May 13, 2026 12:00
@renovate renovate Bot force-pushed the renovate/nuget branch from 0de7511 to 3478a05 Compare May 14, 2026 21:02
@sonarqubecloud
Copy link
Copy Markdown

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.

0 participants