conductor-fips

Direct Vulnerabilities

Known vulnerabilities in the conductor-fips 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
  • L
Allocation of Resources Without Limits or Throttling

<3.32.3-r0
  • L
Improper Certificate Validation

<3.32.3-r0
  • L
Uncontrolled Memory Allocation

<3.32.3-r0
  • L
Uncontrolled Recursion

<3.32.3-r0
  • L
Improper Input Validation

<3.32.3-r0
  • L
CVE-2026-54399

<3.32.3-r0
  • L
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')

<3.32.3-r0
  • L
Improper Input Validation

<3.32.3-r0
  • L
CVE-2026-54428

<3.32.3-r0
  • L
Resource Exhaustion

<3.32.2-r0
  • L
CVE-2026-40983

<3.32.2-r0
  • L
CVE-2026-40984

<3.32.2-r0
  • H
Resource Exhaustion

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

<3.32.2-r0
  • L
Resource Exhaustion

<3.32.2-r0
  • H
HTTP Request Smuggling

<3.32.2-r0
  • L
Improper Access Control

<3.32.2-r0
  • H
Missing Release of Resource after Effective Lifetime

<3.32.2-r0
  • L
Resource Exhaustion

<3.32.2-r0
  • M
HTTP Request Smuggling

<3.32.2-r0
  • M
CRLF Injection

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

<3.32.2-r0
  • H
Improper Encoding or Escaping of Output

<3.32.1-r0
  • L
Incomplete Blacklist

<3.32.1-r0
  • L
Improperly Controlled Modification of Dynamically-Determined Object Attributes

<3.32.1-r0
  • M
CVE-2026-41844

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

<3.32.1-r0
  • L
Information Exposure

<3.32.1-r0
  • H
CVE-2024-52979

<3.32.1-r0
  • L
Improper Verification of Cryptographic Signature

<3.32.1-r0
  • L
GHSA-72hv-8253-57qq

<3.32.1-r0
  • H
CVE-2026-41851

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

<3.32.1-r0
  • L
Allocation of Resources Without Limits or Throttling

<3.32.1-r0
  • L
CVE-2025-41249

<3.32.1-r0
  • L
Improper Access Control

<3.32.1-r0
  • L
Server-Side Request Forgery (SSRF)

<3.32.1-r0
  • L
CVE-2026-22741

<3.32.1-r0
  • L
Integer Overflow or Wraparound

<3.32.1-r0
  • L
Incorrect Default Permissions

<3.32.1-r0
  • H
CVE-2026-41848

<3.32.1-r0
  • L
HTTP Request Smuggling

<3.32.1-r0
  • L
CVE-2026-41713

<3.32.1-r0
  • L
Incomplete Blacklist

<3.32.1-r0
  • L
CRLF Injection

<3.32.1-r0
  • M
CVE-2026-41852

<3.32.1-r0
  • M
Improper Validation of Certificate with Host Mismatch

<3.32.1-r0
  • H
CVE-2024-52981

<3.32.1-r0
  • M
Origin Validation Error

<3.32.1-r0
  • L
HTTP Request Smuggling

<3.32.1-r0
  • M
CVE-2026-41845

<3.32.1-r0
  • L
CRLF Injection

<3.32.1-r0
  • H
Improper Handling of Exceptional Conditions

<3.32.1-r0
  • L
Resource Exhaustion

<3.32.1-r0
  • L
CVE-2025-41234

<3.32.1-r0
  • L
CVE-2026-41841

<3.32.1-r0
  • L
CVE-2026-41850

<3.32.1-r0
  • L
CVE-2025-22233

<3.32.1-r0
  • L
CVE-2026-40973

<3.32.1-r0
  • L
Allocation of Resources Without Limits or Throttling

<3.32.1-r0
  • L
Resource Exhaustion

<3.32.1-r0
  • L
CVE-2026-41853

<3.32.1-r0
  • L
CVE-2026-41840

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

<3.32.1-r0
  • L
CVE-2026-41842

<3.32.1-r0
  • M
Information Exposure Through Log Files

<3.32.1-r0
  • H
Improper Handling of Highly Compressed Data (Data Amplification)

<3.32.1-r0
  • L
Use of Insufficiently Random Values

<3.32.1-r0
  • H
HTTP Request Smuggling

<3.32.1-r0
  • H
Missing Encryption of Sensitive Data

<3.32.1-r0
  • M
Improper Certificate Validation

<3.32.1-r0
  • M
Information Exposure Through Log Files

<3.32.1-r0
  • M
Allocation of Resources Without Limits or Throttling

<3.32.1-r0
  • H
Resource Exhaustion

<3.32.1-r0
  • L
CVE-2025-22227

<3.32.1-r0
  • H
CVE-2024-23450

<3.32.1-r0
  • L
CVE-2026-22740

<3.32.1-r0
  • H
Improper Output Neutralization for Logs

<3.32.1-r0
  • L
CVE-2026-41843

<3.32.1-r0
  • H
HTTP Request Smuggling

<3.32.1-r0
  • L
CVE-2025-41242

<3.32.1-r0
  • L
CVE-2026-22735

<3.32.1-r0
  • L
CVE-2026-22745

<3.32.1-r0
  • H
HTTP Response Splitting

<3.32.1-r0
  • L
CVE-2026-22746

<3.32.1-r0
  • M
CVE-2026-41846

<3.32.1-r0
  • L
Server-Side Request Forgery (SSRF)

<3.32.1-r0
  • L
CVE-2026-41839

<3.32.1-r0
  • L
GHSA-r7wm-3cxj-wff9

<3.32.1-r0
  • L
Resource Exhaustion

<3.32.1-r0
  • L
CVE-2026-22737

<3.32.1-r0
  • H
Resource Exhaustion

<3.32.1-r0
  • C
HTTP Request Smuggling

<3.32.1-r0
  • C
Insufficient Verification of Data Authenticity

<3.32.1-r0
  • C
Insufficient Verification of Data Authenticity

<3.32.1-r0
  • C
HTTP Request Smuggling

<3.32.1-r0
  • C
Improper Input Validation

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

<3.32.1-r0
  • L
Authentication Bypass

*
  • L
Improper Input Validation

*
  • L
CVE-2025-27817

<3.32.1-r0
  • L
Improper Authorization

*