Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET NuGet

GHSA-7jxj-rpx7-ph2c

LOW

Umbraco.Forms CDN may cache sensitive form uploads when processed by ImageSharp

Published
Jan 22, 2026
Updated
Feb 3, 2026
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed

Blast Radius

3 pkgs affected
.NETUmbraco.Forms.NETUmbraco.Forms.NETUmbraco.Forms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Protected files uploaded through Umbraco Forms may be served to unauthenticated users when a CDN or caching layer is present and ImageSharp processes the request. ImageSharp sets aggressive cache headers by default, which can cause intermediary caches to store and serve files that should require authentication.

Patches

This issue affects all (supported) versions Umbraco Forms and is patched in 13.9.0, 16.4.0 and 17.1.0.

Workarounds

Add middleware to set cache headers for form uploads. Place the following code in your Startup.cs or Program.cs after app.UseStaticFiles() and any image processing middleware:

app.Use(async (context, next) =>
{
    var path = context.Request.Path.Value;

    if (!string.IsNullOrEmpty(path) && path.StartsWith("/media/forms/upload/", StringComparison.OrdinalIgnoreCase))
    {
        context.Response.OnStarting(() =>
        {
            context.Response.Headers["Cache-Control"] = "private, no-store, no-cache, must-revalidate";
            context.Response.Headers["Pragma"] = "no-cache";
            context.Response.Headers["Expires"] = "0";
            return Task.CompletedTask;
        });
    }

    await next();
});

Alternatively, configure your CDN to bypass caching for URLs matching /media/forms/upload/*.

Note: The vulnerability requires:

  • A CDN in front of the website
  • An authenticated user having previously requested the image
  • Knowledge of the form GUID, entry GUID, and image filename

If no CDN is in use, this vulnerability does not apply.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetUmbraco.Formsall versions13.9.0
.NETNuGetUmbraco.Forms14.0.0-beta001&&< 16.4.016.4.0
.NETNuGetUmbraco.Forms17.0.0-rc1&&< 17.1.017.1.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Umbraco.Forms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update Umbraco.Forms to 13.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7jxj-rpx7-ph2c is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-7jxj-rpx7-ph2c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7jxj-rpx7-ph2c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Protected files uploaded through Umbraco Forms may be served to unauthenticated users when a CDN or caching layer is present and ImageSharp processes the request. ImageSharp sets aggressive cache headers by default, which can cause intermediary caches to store and serve files that should require authentication. ### Patches This issue affects all (supported) versions Umbraco Forms and is patched in 13.9.0, 16.4.0 and 17.1.0. ### Workarounds Add middleware to set cache headers for form uploads. Place the following code in your `Startup.cs` or `Program.cs` after `app.UseStaticFiles()
O3 Security · Impact-Aware SCA

Is GHSA-7jxj-rpx7-ph2c in your dependencies?

O3 detects GHSA-7jxj-rpx7-ph2c across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.