Skip to main content
Vulnerability Database/CVE-2026-112044

CVE-2026-112044: dotnet eShop Auth Bypass Vulnerability

CVE-2026-112044 is an authentication bypass flaw in dotnet eShop Catalog API affecting the AddApplicationServices function. Attackers can exploit this remotely to circumvent authentication controls. This article covers technical details, affected versions, impact assessment, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-112044 Overview

CVE-2026-112044 is an improper authentication vulnerability [CWE-287] in the dotnet eShop reference application. The flaw resides in the AddApplicationServices function within src/Catalog.API/Extensions/Extensions.cs, part of the Catalog API component. Attackers can exploit the issue remotely over the network without authentication or user interaction. The vulnerability affects builds up to commit 913acea66708a59595351174cee9b29f37179d29. The maintainers were notified through a public issue report but have not responded at the time of disclosure.

Critical Impact

Remote attackers can bypass authentication controls in the Catalog API, exposing confidentiality, integrity, and availability of catalog data in deployments based on the vulnerable dotnet eShop reference code.

Affected Products

  • dotnet/eShop reference application up to commit 913acea66708a59595351174cee9b29f37179d29
  • Catalog API component (src/Catalog.API/Extensions/Extensions.cs)
  • Forks and derivative applications reusing the vulnerable AddApplicationServices configuration

Discovery Timeline

  • 2026-10-19 - CVE-2026-112044 published to NVD
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-112044

Vulnerability Analysis

The vulnerability is categorized as improper authentication [CWE-287] in the Catalog API service of the dotnet eShop reference e-commerce application. The AddApplicationServices function in src/Catalog.API/Extensions/Extensions.cs registers service and middleware dependencies during application startup. Because the registration does not correctly enforce authentication requirements on the Catalog API, requests reach protected handlers without valid credentials.

The attack vector is remote and requires no privileges or user interaction. An attacker with network access to the Catalog API endpoint can issue requests directly and receive responses that should be gated behind authentication. The impact extends to confidentiality, integrity, and availability of catalog data served by the API.

Root Cause

The root cause lies in how authentication is wired up during dependency injection and middleware configuration inside AddApplicationServices. The function fails to apply or correctly bind authentication requirements to the Catalog API's HTTP pipeline. As a result, endpoints that should require authenticated identity are reachable anonymously.

Attack Vector

Exploitation requires only network reachability to the exposed Catalog API. An attacker crafts HTTP requests to Catalog API endpoints and bypasses the expected identity checks. No credentials, tokens, or prior access are needed. See the GitHub eShop Issue #997 and the VulDB CVE-2026-112044 entry for additional technical context.

No public proof-of-concept exploit code has been verified. The vulnerability mechanism is described in prose because no sanitized exploit example is available from authoritative sources.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-112044

Indicators of Compromise

  • Unauthenticated HTTP requests to Catalog API routes returning HTTP 200 responses instead of 401 or 403.
  • Access log entries for Catalog API endpoints with missing or malformed Authorization headers.
  • Unusual request volume against /api/catalog style endpoints originating from untrusted networks.

Detection Strategies

  • Review the Catalog API service for the presence of AddApplicationServices registration from commit 913acea66708a59595351174cee9b29f37179d29 or earlier.
  • Perform authenticated versus anonymous probing of Catalog API endpoints to confirm whether anonymous access is permitted.
  • Audit middleware ordering in Program.cs and Extensions.cs to verify UseAuthentication and UseAuthorization are invoked before endpoint mapping.

Monitoring Recommendations

  • Forward Catalog API access logs to a centralized SIEM and alert on 2xx responses without an authenticated principal.
  • Monitor east-west traffic to Catalog API pods or containers for direct access that bypasses the ingress gateway.
  • Track changes to src/Catalog.API/Extensions/Extensions.cs in source control to catch regressions of the authentication fix.

How to Mitigate CVE-2026-112044

Immediate Actions Required

  • Restrict network exposure of the Catalog API to internal service meshes or authenticated gateways only.
  • Place the Catalog API behind an API gateway that enforces token validation before requests reach the service.
  • Audit forks and internal builds of dotnet/eShop for the vulnerable AddApplicationServices implementation.

Patch Information

No official patch has been released. The maintainers of the dotnet/eShop repository have not responded to the public issue report at the time of CVE publication. Monitor the dotnet/eShop repository and issue #997 for an upstream fix.

Workarounds

  • Add explicit [Authorize] attributes to Catalog API controllers and minimal API endpoints to enforce authentication at the handler level.
  • Configure the ASP.NET Core authentication middleware to require authenticated users by default using a fallback authorization policy.
  • Deploy a reverse proxy or service mesh policy that rejects unauthenticated requests to the Catalog API path.
  • Remove or firewall off direct external exposure of the Catalog API service port until the upstream fix is available.
bash
# Configuration example: enforce authentication as the default policy in Program.cs
# builder.Services.AddAuthorization(options =>
# {
#     options.FallbackPolicy = new AuthorizationPolicyBuilder()
#         .RequireAuthenticatedUser()
#         .Build();
# });
#
# app.UseAuthentication();
# app.UseAuthorization();

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.