Skip to content
Fencer Vulns
low 3.4

CVE-2026-44405 json

Paramiko rsakey.py allows the SHA-1 algorithm

published 2026-05-05 6 mo ago modified 2026-11-07 2 d ago also GHSA-r374-rxx8-8654 , PYSEC-2026-2858 , EUVD-2026-27514

cvss
3.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 1%
public exploits
0
none known

Summary

In Paramiko through 4.0.0 before a448945, rsakey.py allows the SHA-1 algorithm.

Patch / fix

  • pypi paramiko 5.0.0
  • paramiko Debian 14 5.0.0-1

debian advisories DEBIAN-CVE-2026-44405

  • python3-paramiko SLE Module for Basesystem 15 SP7 3.4.0-150400.9.9.1
  • python-paramiko SLE Module for Public Cloud 15 SP4 3.4.0-150400.13.13.1
  • python-paramiko SLE Module for Python 3 15 SP7 3.5.1-150700.20.6.1
  • python-paramiko SLES for SAP applications 16.0, SLES 16.0 3.5.1-160000.3.1

suse advisories SUSE-SU-2026:4618-1SUSE-SU-2026:3093-1SUSE-SU-2026:3031-1SUSE-SU-2026:22192-1

  • python-paramiko openSUSE Leap 16.0 3.5.1-160000.3.1
  • python-paramiko openSUSE Tumbleweed 5.0.0-1.1

opensuse advisories openSUSE-SU-2026:21127-1openSUSE-SU-2026:11025-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-44405 updated cvss 3.4

paramiko: Paramiko: Data integrity could be compromised due to SHA-1 algorithm use

  • Red Hat Migration Toolkit for Containers rhmtc/openshift-migration-hook-runner-rhel8 Red Hat Ansible Automation Platform 2 ansible-automation-platform-24/ee-minimal-rhel8, ansible-automation-platform-24/ee-minimal-rhel9, ansible-automation-platform-25/ee-minimal-rhel8, ansible-automation-platform-25/ee-minimal-rhel9, ansible-automation-platform-26/ee-minimal-rhel9, ansible-automation-platform-24/ee-supported-rhel8, +9 more Red Hat Ansible Automation Platform Ansible Core 2 ansible-automation-platform/ee-minimal-rhel8, ansible-automation-platform/ee-minimal-rhel9, ansible-automation-platform-tech-preview/ee-minimal-rhel8, ansible-automation-platform-tech-preview/ee-minimal-rhel9 Red Hat Discovery 2 discovery/discovery-server-rhel9 Red Hat Enterprise Linux 9 rhel9/bootc-image-builder Red Hat OpenShift AI (RHOAI) rhoai/odh-mlflow-rhel9, rhoai/odh-openvino-model-server-rhel9, rhoai/odh-pipeline-runtime-minimal-cpu-py312-rhel9, rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9, rhoai/odh-pipeline-runtime-pytorch-rocm-py312-rhel9, rhoai/odh-workbench-jupyter-minimal-cpu-py312-rhel9, +14 more
    +3 more products
    Red Hat OpenShift Container Platform 4 openshift4/ose-dpu-intel-ipu-p4sdk-rhel9 Red Hat OpenStack Platform 18.0 rhoso-operators/ee-openstack-ansible-ee-rhel9 Red Hat Satellite 6 satellite/iop-advisor-engine-rhel9, satellite/iop-insights-engine-rhel9
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 6 python-paramiko Red Hat Enterprise Linux 7 python-paramiko Red Hat OpenStack Platform 16.2 python-paramiko, python3-paramiko Red Hat OpenStack Platform 17.1 python-paramiko, python3-paramiko Red Hat OpenStack Platform 18.0 python-paramiko
    under investigation
  • Red Hat Hardened Images mariadb11.8 11.8.6-2.2.hum1
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
6 mo ago

Exploit prediction

0.11% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.4 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N
GitHub 3.1 3.4 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N
OSV 3.1 3.4 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
pypi paramiko
<5.0.0
<=4.0.0
5.0.0

Affected products

  • Paramiko Paramiko

Classification

Weakness
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.