What is the CVSS score of CVE-2026-44662?

CVE-2026-44662 has a CVSS 4.0 base score of 5.1 (Medium). CVSS vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N. EPSS exploitation probability: 0.0%.

Is there a patch available for CVE-2026-44662?

Yes, a patch is available for CVE-2026-44662. Update the affected software to the latest version immediately.

rust-openssl CVE-2026-44662

EUVD-2026-30482 MEDIUM

Heap-based Buffer Overflow (CWE-122)

2026-05-07 https://github.com/rust-openssl/rust-openssl

GHSA-xv59-967r-8726

Buffer Overflow Heap Overflow OpenSSL Suse

5.1

CVSS 4.0 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Attacker crafts request with non-multiple-of-8 plaintext
Delivery

Application calls cipher_update_vec with EVP_aes_*_wrap_pad
Exploit

rust-openssl allocates undersized output buffer
Execution

OpenSSL writes padding and ciphertext beyond buffer boundary
Persist

Heap corruption occurs
Impact

Potential code execution or information disclosure

Vulnerability Assessment

Weakness	CWE CWE-122 ASVS 5.0 V15 - Secure Coding and Architecture Heap buffer bounds checking MITRE ATT&CK 1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	Exploitation requires: (1) application code explicitly calls CipherCtxRef::cipher_update, CipherCtxRef::cipher_update_vec, or symm::Crypter::update with one of the AES key-wrap-with-padding ciphers (EVP_aes_128_wrap_pad, EVP_aes_192_wrap_pad, or EVP_aes_256_wrap_pad); (2) plaintext input length is not a multiple of 8 bytes; (3) plaintext length is attacker-influenced or attacker can control input data. Standard AES encryption modes (CBC, CTR, GCM) and unpadded key-wrap (EVP_aes_*_wrap without _pad) are not affected. Applications that only use standard symmetric encryption, asymmetric cryptography, or hashing with rust-openssl are not vulnerable.
Impact	This is a high-severity vulnerability despite the missing CVSS score. The attack vector is network-capable if plaintext length is attacker-influenced (e.g., user-supplied key material or wrapped data), the complexity is low (trigger by providing non-multiple-of-8 input), and no authentication or user interaction is required. Heap corruption is a direct consequence that can enable arbitrary code execution, information disclosure, or denial of service depending on heap layout and attacker control. However, real-world risk is constrained by two factors: (1) the vulnerability only affects applications explicitly using AES key-wrap-with-padding ciphers-a niche use case primarily for cryptographic key protection, not general encryption; (2) exploitation requires attacker control over plaintext length, which may not exist in all deployments. This is not a false-positive high-CVSS issue, but rather a legitimate critical vulnerability with a narrower attack surface than network-facing code might suggest. No public exploit code or KEV listing has been identified, indicating this is a responsibly disclosed issue not yet weaponized.
Exploit ScenarioDerived	An attacker sending a crafted key-wrapping request with a non-multiple-of-8 byte plaintext length to a Rust application using rust-openssl's CipherCtxRef::cipher_update_vec or symm::Crypter::update with AES key-wrap-with-padding triggers OpenSSL to write 1-7 bytes into heap memory beyond the allocated buffer. If the application subsequently processes or returns heap data, the attacker may extract sensitive information; if the corrupted heap contains control structures or function pointers, the attacker may achieve code execution. The attack requires no network authentication or user interaction if the application exposes plaintext length as a parameter.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).

Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 07, 2026

Heap buffer overflow in rust-openssl's AES key-wrap-with-padding cipher functions allows attackers to write up to 7 bytes past allocated buffer boundaries when processing non-multiple-of-8 plaintext inputs, enabling attacker-controlled heap corruption. Affected versions 0.10.0 through 0.10.78 are vulnerable when CipherCtxRef::cipher_update, CipherCtxRef::cipher_update_vec, or symm::Crypter::update are used with EVP_aes_128/192/256_wrap_pad ciphers.

RemediationAI

Upgrade rust-openssl to version 0.10.79 or later immediately. This can typically be done by updating the Cargo.toml dependency to openssl = "0.10.79" or higher and running cargo update. No workarounds exist for versions prior to 0.10.79 if AES key-wrap-with-padding ciphers are in use; affected code paths must be disabled or removed entirely. If upgrading is not immediately feasible, the only mitigation is to refrain from using EVP_aes_128_wrap_pad, EVP_aes_192_wrap_pad, or EVP_aes_256_wrap_pad ciphers until the patch is applied. Validate that input plaintext length is always a multiple of 8 bytes as a temporary compensating control, though this does not fully eliminate the heap corruption risk if the underlying OpenSSL behavior changes. See vendor advisory at https://github.com/rust-openssl/rust-openssl/security/advisories/GHSA-xv59-967r-8726 for additional details.

Affected VersionsENISA

rust-openssl 0.10.0, < 0.10.79

Affected Packages

cargo openssl fix: 0.10.79

euvd rust_openssl_0_10_0 fix: 0.10.79

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in cargo, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

rust-openssl wraps OpenSSL's EVP cipher interface, exposing AES key-wrap-with-padding ciphers (EVP_aes_128/192/256_wrap_pad) via CipherCtxRef and symm::Crypter APIs. The vulnerability stems from incorrect output buffer allocation logic in these wrapper functions - OpenSSL's key-wrap padding mechanism requires output buffers sized to handle non-standard length requirements, but rust-openssl miscalculates required output size for non-multiple-of-8 inputs. When the underlying OpenSSL EVP_EncryptUpdate writes output, it extends beyond the undersized buffer, causing heap overflow (CWE-122: Heap-based Buffer Overflow). The issue is specific to padded key-wrap ciphers; standard AES modes and unpadded key-wrap are unaffected.

Know when OpenSSL gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 5.1 MEDIUM

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

SUSE 4.8 MEDIUM

AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

Attack Vector

Local

Attack Complexity

Low

Attack Requirements

None

Privileges Required

None

User Interaction

None

Vulnerable system: Confidentiality

None

Vulnerable system: Integrity

Low

Vulnerable system: Availability

Low

Subsequent system: Confidentiality

None

Subsequent system: Integrity

None

Subsequent system: Availability

None

Lifecycle Timeline

CVSS changed

May 14, 2026 - 21:22 NVD

5.1 (MEDIUM)

CVE Published

May 07, 2026 - 22:33 nvd

MEDIUM

DescriptionGitHub Advisory

CipherCtxRef::cipher_update, CipherCtxRef::cipher_update_vec, and symm::Crypter::update incorrectly sized output buffers when used with AES key-wrap-with-padding ciphers (EVP_aes_{128,192,256}_wrap_pad). For a non-multiple-of-8 input, OpenSSL writes up to 7 bytes past the end of the caller's buffer or Vec, producing attacker-controllable heap corruption when the plaintext length is attacker-influenced.

This only impacts users using AES key-wrap-with-padding ciphers.

Threat Intelligence Overview

EPSS Score

0.0%

Top 97% exploitable

Threat Intel

1 sources

Data Quality

7 sources

Confidence: High

EUVD

NVD

CVE.org

EPSS

Vulnrichment GHSA MSRC Vendor

GitHub

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity MEDIUM

CISA KEV No

Public POC No

EPSS 0.0%

Patch available Yes

Active threat No

Deciding rule

MEDIUM severity (CVSS 4.0-6.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation

None

System Exposure· derived

Small

Automatable

Yes

Human Impact· derived

Medium

Technical Impact

Total

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +26

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Buffer Overflow HIGH

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Heap Overflow HIGH

A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.

More in OpenSSL

View all

CVE-2014-0160 HIGH Act Now POC

7.5 Apr 07

The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe

CVE-2021-3711 CRITICAL Act Now POC

9.8 Aug 24

In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Rated cri

CVE-2014-0195 MEDIUM This Month POC

6.8 Jun 05

The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0

CVE-2014-0224 HIGH Act Now POC

7.4 Jun 05

OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph

CVE-2016-0800 MEDIUM This Month POC

5.9 Mar 01

The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to se

CVE-2015-0204 MEDIUM This Month POC

4.3 Jan 09

The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k

CVE-2022-2068 HIGH Act Now

7.3 Jun 21

In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehas

CVE-2015-4000 LOW Monitor POC

3.7 May 21

The TLS protocol 1.2 and earlier, when a DHE_EXPORT ciphersuite is enabled on a server but not on a client, does not pro

CVE-2014-3566 LOW Monitor POC

3.4 Oct 15

The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which mak

CVE-2016-2107 MEDIUM This Month POC

5.9 May 05

The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a

CVE-2015-1793 MEDIUM This Month POC

6.5 Jul 09

The X509_verify_cert function in crypto/x509/x509_vfy.c in OpenSSL 1.0.1n, 1.0.1o, 1.0.2b, and 1.0.2c does not properly

CVE-2022-3602 HIGH Act Now

7.5 Nov 01

A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Rated hig

Same weakness CWE-122 – Heap-based Buffer Overflow

View all

CVE-2023-4911 HIGH POC

7.8

CVE-2023-27997 CRITICAL

9.8

CVE-2026-94127 CRITICAL POC

9.3

CVE-2025-25249 CRITICAL POC

9.8

CVE-2026-85880 HIGH POC

7.8

CVE-2025-24985 HIGH POC

7.8

CVE-2026-53362 HIGH POC

7.8

CVE-2025-21418 HIGH

7.8

Same technique Buffer Overflow

View all

CVE-2017-7269 CRITICAL POC

9.8

CVE-2015-5119 CRITICAL POC

9.8

CVE-2015-3113 CRITICAL POC

9.8

CVE-2011-2462 CRITICAL POC

9.8

CVE-2020-0796 CRITICAL POC

10.0

CVE-2019-11043 CRITICAL POC

9.8

CVE-2009-0927 HIGH POC

8.8

CVE-2012-1889 HIGH POC

8.8

Vendor StatusVendor

SUSE

Severity: Moderate

Product	Status
Container suse/sl-micro/6.0/baremetal-os-container:latest	Affected
Container suse/sl-micro/6.0/toolbox:latest	Affected
Image SLES15-SP7-Azure-3P Image SLES15-SP7-Azure-Basic Image SLES15-SP7-Azure-Standard Image SLES15-SP7-BYOS-Azure Image SLES15-SP7-BYOS-GCE Image SLES15-SP7-CHOST-BYOS-Aliyun Image SLES15-SP7-CHOST-BYOS-Azure Image SLES15-SP7-CHOST-BYOS-EC2 Image SLES15-SP7-CHOST-BYOS-GDC Image SLES15-SP7-CHOST-BYOS-SAP-CCloud Image SLES15-SP7-EC2 Image SLES15-SP7-EC2-ECS-HVM Image SLES15-SP7-GCE Image SLES15-SP7-HPC-Azure Image SLES15-SP7-HPC-BYOS-Azure Image SLES15-SP7-HPC-BYOS-EC2 Image SLES15-SP7-HPC-BYOS-GCE Image SLES15-SP7-Hardened-BYOS-Azure Image SLES15-SP7-Hardened-BYOS-EC2 Image SLES15-SP7-Hardened-BYOS-GCE Image SLES15-SP7-SAP-Azure Image SLES15-SP7-SAP-Azure-3P Image SLES15-SP7-SAP-BYOS-Azure Image SLES15-SP7-SAP-BYOS-EC2 Image SLES15-SP7-SAP-BYOS-GCE Image SLES15-SP7-SAP-EC2 Image SLES15-SP7-SAP-GCE Image SLES15-SP7-SAP-Hardened-Azure Image SLES15-SP7-SAP-Hardened-BYOS-Azure Image SLES15-SP7-SAP-Hardened-BYOS-EC2 Image SLES15-SP7-SAP-Hardened-BYOS-GCE Image SLES15-SP7-SAP-Hardened-GCE Image SLES15-SP7-SAPCAL-Azure Image SLES15-SP7-SAPCAL-EC2 Image SLES15-SP7-SAPCAL-GCE	Affected
SUSE Linux Enterprise Desktop 15 SP7	Fixed
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS	Fixed

References

Advisories & patches

Search Externally

GitHub PoC

Exploit-DB PacketStorm Snyk Rapid7 Nuclei Templates Trickest PoC

Back