Information Exposure Through Caching Affecting dotnet-sdk-7.0-source-built-artifacts package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL9-DOTNETSDK70SOURCEBUILTARTIFACTS-12424391
- published1 Sept 2025
- disclosed29 Aug 2025
Introduced: 29 Aug 2025
NewCVE-2025-57752 (opens in a new tab)How to fix?
There is no fixed version for RHEL:9 dotnet-sdk-7.0-source-built-artifacts.
NVD Description
Note: Versions mentioned in the description apply only to the upstream dotnet-sdk-7.0-source-built-artifacts package and not the dotnet-sdk-7.0-source-built-artifacts package as distributed by RHEL.
See How to fix? for RHEL:9 relevant fixed versions and status.
Next.js is a React framework for building full-stack web applications. In versions before 14.2.31 and from 15.0.0 to before 15.4.5, Next.js Image Optimization API routes are affected by cache key confusion. When images returned from API routes vary based on request headers (such as Cookie or Authorization), these responses could be incorrectly cached and served to unauthorized users due to a cache key confusion bug. This vulnerability has been fixed in Next.js versions 14.2.31 and 15.4.5. All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled.