Cyber Resilience

CVE-2026-5479

Published
10 April 2026
Modified
13 April 2026
CVSS Score v4 7.6
Click a component to see what it means
Raw vectorCVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0015 5th percentile
Risk Priority 34 floored blend · peak EPSS

Summary

CVE-2026-5479 is a high-severity Improper Validation of Integrity Check Value (CWE-354) vulnerability. Its CVSS base score is 7.6 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Supply Chain Compromise (T1195); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-5479 is a vulnerability in the wolfSSL cryptographic library's EVP layer, specifically affecting the ChaCha20-Poly1305 AEAD decryption path in the wolfSSL_EVP_CipherFinal function and related EVP cipher finalization functions. The issue arises because the implementation computes or accepts the authentication tag during decryption but fails to verify it against the expected value before returning plaintext to the caller. This flaw, classified under CWE-354 (Improper Validation of Integrity Check Value), impacts applications that use the wolfSSL EVP API for ChaCha20-Poly1305 decryption.

An attacker can exploit this vulnerability by supplying a malformed or tampered ciphertext to an application performing ChaCha20-Poly1305 decryption via the affected wolfSSL EVP functions. Since the authentication tag is not properly checked, the application will accept invalid plaintext as authentic, potentially allowing the attacker to decrypt and process forged or modified data without detection. Exploitation requires the attacker to have the ability to provide ciphertext input to the decryption routine, such as in network protocols or file processing scenarios that rely on wolfSSL for this cipher suite.

A pull request addressing the issue is available at https://github.com/wolfSSL/wolfssl/pull/10102, which presumably implements the necessary authentication tag verification fix for the EVP layer's ChaCha20-Poly1305 decryption path. Security practitioners should review and apply this patch to affected wolfSSL versions to mitigate the risk.

EU & UK References

Vulnerability Data

In wolfSSL's EVP layer, the ChaCha20-Poly1305 AEAD decryption path in wolfSSL_EVP_CipherFinal (and related EVP cipher finalization functions) fails to verify the authentication tag before returning plaintext to the caller. When an application uses the EVP API to perform ChaCha20-Poly1305 decryption,…

more

the implementation computes or accepts the tag but does not compare it against the expected value.

CWE(s)
CWE-354

Related Threats

MITRE ATT&CK Enterprise Techniques

T1195 Supply Chain Compromise Initial Access
Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise.
attack.mitre.org →
T1195.001 Compromise Software Dependencies and Development Tools Initial Access
Adversaries may manipulate software dependencies and development tools prior to receipt by a final consumer for the purpose of data or system compromise.
attack.mitre.org →
T1195.002 Compromise Software Supply Chain Initial Access
Adversaries may manipulate application software prior to receipt by a final consumer for the purpose of data or system compromise.
attack.mitre.org →
T1565 Data Manipulation Impact
Adversaries may insert, delete, or manipulate data in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
attack.mitre.org →
T1565.002 Transmitted Data Manipulation Impact
Adversaries may alter data en route to storage or other systems in order to manipulate external outcomes or hide activity, thus threatening the integrity of the data.
attack.mitre.org →
T1601 Modify System Image Defense Impairment
Adversaries may make changes to the operating system of embedded network devices to weaken defenses and provide new capabilities for themselves.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-32883Shared CWE-354
CVE-2026-12816Shared CWE-354
CVE-2024-47255Shared CWE-354
CVE-2023-31438Shared CWE-354
CVE-2026-34182Shared CWE-354
CVE-2024-46992Shared CWE-354
CVE-2023-33668Shared CWE-354
CVE-2023-31437Shared CWE-354
CVE-2023-28802Shared CWE-354
CVE-2024-47089Shared CWE-354

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 10 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V10.4.12

Mitigating Controls (NIST 800-53 r5) AI

SI-7 Software, Firmware, and Information Integrity good match

Requires integrity verification tools that detect unauthorized changes when checksum validation is missing or flawed.

SC-13 Cryptographic Protection good match

Mandates cryptographic mechanisms that include integrity protection, preventing improper checksum validation.

SC-8 Transmission Confidentiality and Integrity good match

Requires protection of transmitted information integrity, directly mandating correct validation of integrity checks.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-01 mostly match
prevents

Requires cryptographic hashes and signatures that directly enforce integrity-check validation for data at rest.

PR.DS-02 mostly match
prevents

Requires cryptographic hashes and signatures that directly enforce integrity-check validation for data in transit.

ID.RA-09 partial match
prevents

Mandates pre-acquisition integrity assessment, addressing only the initial portion of the weakness lifecycle.

RC.RP-03 partial match
prevents

Requires verification of backup integrity, covering validation only within recovery scenarios.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.24 Use of cryptography mostly match
prevents

Cryptographic controls mandate integrity mechanisms whose correct validation directly prevents CWE-354.

A.8.28 Secure coding mostly match
prevents

Secure coding standards require proper implementation and validation of checksums or MACs.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect missing integrity validation but does not itself implement the control.

A.8.26 Application security requirements partial match
prevents

Application security requirements include integrity checks on messages and data, mitigating improper validation.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (2 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-354
  • V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-354
Oracle Linux 9 (1 rule)
  • V-271523 OL 9 must check the GPG signature of locally installed software packages before installation. prevents CWE-354
RHEL 7 (2 rules)
  • V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-354
  • V-204448 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-354
RHEL 8 (2 rules)
  • V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-354
  • V-230265 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-354

References