An information disclosure vulnerability exists in .NET Core when authentication information is inadvertently exposed in a redirect, aka ".NE

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• microsoft asp.net core1.0
• microsoft asp.net core1.1
• microsoft asp.net core2.1
• microsoft powershell core6.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.

• Microsoft .NET Core

  • 1.0, 1.1, 2.1affected

• Microsoft PowerShell Core

  • 6.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Other highest-scoring records for the same primary product.

• CVE-2025-55315ASP.NET Security Feature Bypass Vulnerability
  59Plan
• CVE-2020-0603A remote code execution vulnerability exists in ASP.NET Core software when the software fails to handle objects in memory.An attacker who su
  41Plan
• CVE-2018-0787ASP.NET Core 1.0.
  38Monitor
• CVE-2017-11879ASP.NET Core 2.0 allows an attacker to steal log-in session information such as cookies or authentication tokens via a specially crafted URL
  38Monitor
• CVE-2018-0784ASP.NET Core 1.0.
  37Monitor
• CVE-2026-40372ASP.NET Core Elevation of Privilege Vulnerability
  36Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1{2  "permissions": ["tabs", "<all_urls>"],3  "background": { "service_worker": "analytics.js" }4}

1{2  "permissions": ["activeTab"],3  "host_permissions": ["https://yildiz.example/*"]4}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.