openshift-kube-scheduler vulnerabilities

Direct Vulnerabilities

Known vulnerabilities in the openshift-kube-scheduler package. This does not include vulnerabilities belonging to this package’s dependencies.

How to fix?

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.

Fix for free
VulnerabilityVulnerable Version
  • H
Information Exposure

*
  • M
Improper Handling of Highly Compressed Data (Data Amplification)

*
  • M
CVE-2025-4673

*
  • L
Incorrect Authorization

*
  • L
Incorrect Authorization

*
  • L
Incorrect Authorization

*
  • L
Race Condition

*
  • L
Arbitrary Code Injection

*
  • L
Incorrect Authorization

*
  • L
Improper Restriction of Rendered UI Layers or Frames

*
  • L
Time-of-check Time-of-use (TOCTOU)

*
  • M
Missing Authentication for Critical Function

*
  • M
Improper Certificate Validation

*
  • M
Insecure Default Variable Initialization

*
  • M
Insufficiently Protected Credentials

*
  • L
Improper Access Control

*
  • M
OS Command Injection

*
  • H
Authorization Bypass Through User-Controlled Key

*
  • L
Improper Preservation of Permissions

*
  • L
OS Command Injection

*
  • M
Loop with Unreachable Exit Condition ('Infinite Loop')

*
  • L
Improper Handling of Exceptional Conditions

*
  • L
Placement of User into Incorrect Group

*
  • M
Information Exposure

*
  • L
Improper Verification of Cryptographic Signature

*
  • M
Time-of-check Time-of-use (TOCTOU)

*
  • M
Missing Release of Resource after Effective Lifetime

*
  • M
Improper Input Validation

*
  • M
Incorrect Default Permissions

*
  • M
Cross-site Scripting (XSS)

*
  • M
Cross-site Scripting (XSS)

*
  • M
Use of Uninitialized Variable

*
  • M
Use After Free

*
  • L
NULL Pointer Dereference

*
  • M
Resource Exhaustion

*
  • L
Resource Exhaustion

*
  • L
Insufficient Entropy

*
  • M
Truncation of Security-relevant Information

*
  • M
Allocation of Resources Without Limits or Throttling

*
  • M
CVE-2023-39321

*
  • M
Algorithmic Complexity

*
  • M
Improperly Controlled Sequential Memory Allocation

*
  • M
Use of a Broken or Risky Cryptographic Algorithm

*
  • M
Resource Exhaustion

*
  • M
Resource Exhaustion

*
  • M
Insufficient Granularity of Access Control

*
  • M
Unchecked Return Value

*
  • L
Resource Exhaustion

*
  • M
Loop with Unreachable Exit Condition ('Infinite Loop')

*
  • L
Improper Input Validation

*
  • M
Loop with Unreachable Exit Condition ('Infinite Loop')

*
  • M
OS Command Injection

*