CVE-2026-5295: A stack buffer overflow exists in wolfSSL's PKCS7 implementation in the wc_PKCS7_DecryptOri() function in wolf

Q: How do I fix CVE-2026-5295?

wolfssl: upgrade to 5.9.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-5295 being exploited?

CVE-2026-5295 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-5295 affect?

CVE-2026-5295 affects wolfssl. Severity is high (CVSS 8.0). A stack buffer overflow exists in wolfSSL's PKCS7 implementation in the wc_PKCS7_DecryptOri() function in wolfcrypt/src/pkcs7.c. When processing a CMS EnvelopedData message containing an OtherRecipientInfo (ORI) recipient, the function copi

Routine

HIGH 8.0UPGRADE

CVE-2026-5295 is a high-severity flaw (CVSS 8.0) affecting wolfssl. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A stack buffer overflow exists in wolfSSL's PKCS7 implementation in the wc_PKCS7_DecryptOri() function in wolfcrypt/src/pkcs7.c. When processing a CMS EnvelopedData message containing an OtherRecipientInfo (ORI) recipient, the function copies an ASN.1-parsed OID into a fixed 32-byte stack buffer (oriOID[MAX_OID_SZ]) via XMEMCPY without first validating that the parsed OID length does not exceed MAX_OID_SZ. A crafted CMS EnvelopedData message with

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.0 (High)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 93%)
CISA exploited list	No
Weakness	CWE-121
Published	2026-04-09
Last modified	2026-06-17

Publisher (CNA): wolfSSL Inc. · Vendor: wolfssl

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-09 23:17 UTCPublished CVE record published
2026-06-17 10:58 UTCUpdated Record last modified

wolfssl wolfssl UPGRADE

Affected: < 5.9.1

Fixed in: 5.9.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wolfssl || rpm -q wolfssl || wolfssl --version

2. UPGRADE to 5.9.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wolfssl

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wolfssl

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-5295?

wolfssl: upgrade to 5.9.1. Exact commands for each OS are on this page.

Is CVE-2026-5295 being exploited?

CVE-2026-5295 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-5295 affect?

CVE-2026-5295 affects wolfssl. Severity is high (CVSS 8.0). A stack buffer overflow exists in wolfSSL's PKCS7 implementation in the wc_PKCS7_DecryptOri() function in wolfcrypt/src/pkcs7.c. When processing a CMS EnvelopedData message containing an OtherRecipientInfo (ORI) recipient, the function copi

How urgent is CVE-2026-5295?

Priority 30/100. High severity

Software pages

wolfSSL vulnerabilities

Related CVEs

CVE-2026-55967 HIGH 7.5 UPGRADE AES-GCM encryption/decryption with extremely large cumulative single message sizes (>64 GiB) were not properly
CVE-2026-5263 MEDIUM 6.5 UPGRADE URI nameConstraints from constrained intermediate CAs are parsed but not enforced during certificate chain ver
CVE-2026-7532 HIGH 7.5 UPGRADE iPAddress name constraints bypass when WOLFSSL_IP_ALT_NAME is not defined
CVE-2026-6678 MEDIUM 5.3 UPGRADE Integer underflow in wc_PKCS7_DecryptOri when handling crafted Other Recipient Info, leading to incorrect leng
CVE-2026-6679 HIGH 7.5 UPGRADE A heap buffer overflow could occur in the DTLS 1.3 ACK serialization path before the connecting peer is authen

References

← Back to latest CVEs