Origin Validation Error Affecting dotnet-host package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.01% (1st 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-RHEL9-DOTNETHOST-15713475
  • published21 Mar 2026
  • disclosed17 Mar 2026

Introduced: 17 Mar 2026

NewCVE-2026-27977  (opens in a new tab)
CWE-346  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:9 dotnet-host.

NVD Description

Note: Versions mentioned in the description apply only to the upstream dotnet-host package and not the dotnet-host 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. Starting in version 16.0.1 and prior to version 16.1.7, in next dev, cross-site protection for internal websocket endpoints could treat Origin: null as a bypass case even if allowedDevOrigins is configured, allowing privacy-sensitive/opaque contexts (for example sandboxed documents) to connect unexpectedly. If a dev server is reachable from attacker-controlled content, an attacker may be able to connect to the HMR websocket channel and interact with dev websocket traffic. This affects development mode only. Apps without a configured allowedDevOrigins still allow connections from any origin. The issue is fixed in version 16.1.7 by validating Origin: null through the same cross-site origin-allowance checks used for other origins. If upgrading is not immediately possible, do not expose next dev to untrusted networks and/or block websocket upgrades to /_next/webpack-hmr when Origin is null at the proxy.

CVSS Base Scores

version 3.1