Homepage

Information Exposure Through Caching The advisory has been revoked - it doesn't affect any version of package dotnet7.0  (opens in a new tab)

Threat Intelligence

EPSS
0.35% (27th percentile)

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-RHEL10-DOTNET70-17457328
  • published25 Jun 2026
  • disclosed29 Aug 2025
Report a new vulnerability Found a mistake?

Introduced: 29 Aug 2025

CVE-2025-57752  (opens in a new tab)
CWE-524  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:10.

NVD Description

Note: Versions mentioned in the description apply only to the upstream dotnet7.0 package and not the dotnet7.0 package as distributed by RHEL.

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.