dotnet8-runtime

Direct Vulnerabilities

Known vulnerabilities in the dotnet8-runtime package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free
VulnerabilityVulnerable Version
  • H
Heap-based Buffer Overflow

<8.0.31-r0
  • H
Heap-based Buffer Overflow

<8.0.31-r0
  • M
Protection Mechanism Failure

<8.0.31-r0
  • H
Heap-based Buffer Overflow

<8.0.31-r0
  • H
Heap-based Buffer Overflow

<8.0.31-r0
  • H
Unchecked Return Value

<8.0.31-r0
  • M
Improper Cross-boundary Removal of Sensitive Data

<8.0.31-r0
  • H
Integer Overflow or Wraparound

<8.0.31-r0
  • M
HTTP Request Smuggling

<8.0.31-r0
  • M
Improper Handling of Highly Compressed Data (Data Amplification)

<8.0.31-r0
  • H
Heap-based Buffer Overflow

<8.0.31-r0
  • H
Out-of-bounds Write

<8.0.31-r0
  • M
Origin Validation Error

<8.0.31-r0
  • H
Use After Free

<8.0.31-r0
  • H
Unchecked Input for Loop Condition

<8.0.31-r0
  • H
Access of Resource Using Incompatible Type ('Type Confusion')

<8.0.29-r0
  • H
Allocation of Resources Without Limits or Throttling

<8.0.29-r0
  • H
Deserialization of Untrusted Data

<8.0.29-r0
  • H
Allocation of Resources Without Limits or Throttling

<8.0.29-r0
  • H
Allocation of Resources Without Limits or Throttling

<8.0.29-r0
  • H
Authentication Bypass

<8.0.29-r0
  • H
Improper Validation of Specified Type of Input

<8.0.29-r0
  • L
CVE-2026-56158

<8.0.29-r0
  • H
Allocation of Resources Without Limits or Throttling

<8.0.29-r0
  • M
Link Following

<8.0.29-r0
  • H
Deserialization of Untrusted Data

<8.0.29-r0
  • H
Resource Exhaustion

<8.0.28-r0
  • M
Link Following

<8.0.28-r0
  • H
Stack-based Buffer Overflow

<8.0.29-r0
  • H
Incorrect Implementation of Authentication Algorithm

<8.0.29-r0
  • H
LDAP Injection

<8.0.29-r0
  • H
Arbitrary Code Injection

<8.0.29-r0
  • M
Improper Encoding or Escaping of Output

<8.0.29-r0
  • C
Insufficient Verification of Data Authenticity

<8.0.29-r0
  • H
Improper Authorization

<8.0.28-r0
  • H
Improper Input Validation

<8.0.27-r0
  • H
Loop with Unreachable Exit Condition ('Infinite Loop')

<8.0.27-r0
  • M
Directory Traversal

<8.0.27-r0
  • H
Improper Input Validation

<8.0.27-r0
  • M
Protection Mechanism Failure

<8.0.26-r0
  • H
Resource Exhaustion

<8.0.26-r0
  • H
Improper Input Validation

<8.0.26-r0
  • H
Improper Neutralization of Special Elements

<8.0.26-r0
  • H
Allocation of Resources Without Limits or Throttling

<8.0.25-r0
  • H
Improper Handling of Missing Special Element

<8.0.24-r0
  • H
CVE-2024-35264

<8.0.7-r0
  • M
CVE-2024-38167

<8.0.8-r0
  • H
CVE-2024-26190

<8.0.3-r0
  • C
HTTP Request Smuggling

<8.0.21-r0
  • H
CVE-2024-21386

<8.0.2-r0
  • M
Inadequate Encryption Strength

<8.0.21-r0
  • H
CVE-2024-21404

<8.0.2-r0
  • H
Link Following

<8.0.21-r0
  • H
Untrusted Search Path

<8.0.17-r0
  • H
Buffer Over-read

<8.0.12-r0
  • H
CVE-2025-21172

<8.0.12-r0
  • H
External Control of File Name or Path

<8.0.16-r0
  • H
CVE-2025-24070

<8.0.14-r0
  • H
CVE-2024-38095

<8.0.7-r0
  • H
CVE-2024-20672

<8.0.6-r0
  • H
Allocation of Resources Without Limits or Throttling

<8.0.15-r0
  • H
CVE-2024-43485

<8.0.10-r0
  • H
CVE-2024-30105

<8.0.7-r0
  • H
CVE-2024-43484

<8.0.10-r0
  • M
CVE-2024-30045

<8.0.5-r0
  • H
CVE-2024-38168

<8.0.8-r0
  • L
Race Condition

<8.0.5-r0
  • H
CVE-2024-21409

<8.0.4-r0
  • H
CVE-2024-21392

<8.0.3-r0
  • H
CVE-2025-21173

<8.0.12-r0
  • H
CVE-2024-43483

<8.0.10-r0
  • H
CVE-2024-38229

<8.0.10-r0