No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

<https://pulumi-community.slack.com/archives/CQ2QFLNFL/p1771951355010899> crosspost as it's not only in dotnet provider

It looks like we build language-dotnet with 1.24.7, and this CVE is for &lt;1.24.13 - I'll ask the team :slightly_smiling_face:

OK, this has been updated, and will be fixed in the next release!

Thanks for taking a look. In dockerfile I remove java and yaml directories because they have similar issues

<@U08DQ9T5X5K> when approx. pulumi will be released?

we release every week, so if we've missed this week's release then it'll be mid next week :slightly_smiling_face:

image.png

Hi, I was able to bump pulumi and pulumi-azure-native but there are still CVEs from stdlib

Hi guys, it seems there is new high scored CVE, could you take a look?
Thanks, Grzesiek

Again, we don't use any cryto functions in the dotnet runtime so I wouldn't count this as risky. But it should get picked up in the weeks auto dependency updates for the next release.