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-15715745
  • published21 Mar 2026
  • disclosed17 Mar 2026

Introduced: 17 Mar 2026

NewCVE-2026-27978  (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, origin: null was treated as a "missing" origin during Server Action CSRF validation. As a result, requests from opaque contexts (such as sandboxed iframes) could bypass origin verification instead of being validated as cross-origin requests. An attacker could induce a victim browser to submit Server Actions from a sandboxed context, potentially executing state-changing actions with victim credentials (CSRF). This is fixed in version 16.1.7 by treating 'null' as an explicit origin value and enforcing host/origin checks unless 'null' is explicitly allowlisted in experimental.serverActions.allowedOrigins. If upgrading is not immediately possible, add CSRF tokens for sensitive Server Actions, prefer SameSite=Strict on sensitive auth cookies, and/or do not allow 'null' in serverActions.allowedOrigins unless intentionally required and additionally protected.

CVSS Base Scores

version 3.1