UBUNTU-CVE-2026-5446 (CVE-2026-5446)
Vulnerability from osv_ubuntu – Published: 2026-04-09 21:16 – Updated: 2026-05-20 15:24 – Source website
VLAI
Details
In wolfSSL, ARIA-GCM cipher suites used in TLS 1.2 and DTLS 1.2 reuse an identical 12-byte GCM nonce for every application-data record. Because wc_AriaEncrypt is stateless and passes the caller-supplied IV verbatim to the MagicCrypto SDK with no internal counter, and because the explicit IV is zero-initialized at session setup and never incremented in non-FIPS builds. This vulnerability affects wolfSSL builds configured with --enable-aria and the proprietary MagicCrypto SDK (a non-default, opt-in configuration required for Korean regulatory deployments). AES-GCM is not affected because wc_AesGcmEncrypt_ex maintains an internal invocation counter independently of the call-site guard.
Severity
7.1 (High)
N/A (UNKNOWN)
References
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libcyassl5",
"binary_version": "3.4.8+dfsg-1"
},
{
"binary_name": "libwolfssl0",
"binary_version": "3.4.8+dfsg-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "wolfssl",
"purl": "pkg:deb/ubuntu/wolfssl@3.4.8+dfsg-1?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.4.8+dfsg-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwolfssl15",
"binary_version": "3.13.0+dfsg-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "wolfssl",
"purl": "pkg:deb/ubuntu/wolfssl@3.13.0+dfsg-1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.10.2+dfsg-2",
"3.12.0+dfsg-1",
"3.12.2+dfsg-1",
"3.13.0+dfsg-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwolfssl24",
"binary_version": "4.3.0+dfsg-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "wolfssl",
"purl": "pkg:deb/ubuntu/wolfssl@4.3.0+dfsg-2?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.1.0+dfsg-2",
"4.2.0+dfsg-1",
"4.2.0+dfsg-2",
"4.2.0+dfsg-3",
"4.3.0+dfsg-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwolfssl32",
"binary_version": "5.2.0-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "wolfssl",
"purl": "pkg:deb/ubuntu/wolfssl@5.2.0-2?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.6.0-3",
"5.0.0-1",
"5.1.1-1",
"5.2.0-1",
"5.2.0-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwolfssl42t64",
"binary_version": "5.6.6-1.3build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "wolfssl",
"purl": "pkg:deb/ubuntu/wolfssl@5.6.6-1.3build1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.5.4-2",
"5.5.4-2.1",
"5.6.4-2",
"5.6.6-1.2",
"5.6.6-1.3",
"5.6.6-1.3build1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwolfssl42t64",
"binary_version": "5.7.2-0.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "wolfssl",
"purl": "pkg:deb/ubuntu/wolfssl@5.7.2-0.1?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.7.2-0.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libwolfssl44",
"binary_version": "5.9.1-0.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "wolfssl",
"purl": "pkg:deb/ubuntu/wolfssl@5.9.1-0.1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.7.2-0.1",
"5.8.2-1.2",
"5.8.4-1",
"5.9.1-0.1"
]
}
],
"aliases": [],
"details": "In wolfSSL, ARIA-GCM cipher suites used in TLS 1.2 and DTLS 1.2 reuse an identical 12-byte GCM nonce for every application-data record. Because wc_AriaEncrypt is stateless and passes the caller-supplied IV verbatim to the MagicCrypto SDK with no internal counter, and because the explicit IV is zero-initialized at session setup and never incremented in non-FIPS builds. This vulnerability affects wolfSSL builds configured with --enable-aria and the proprietary MagicCrypto SDK (a non-default, opt-in configuration required for Korean regulatory deployments). AES-GCM is not affected because wc_AesGcmEncrypt_ex maintains an internal invocation counter independently of the call-site guard.",
"id": "UBUNTU-CVE-2026-5446",
"modified": "2026-05-20T15:24:32Z",
"published": "2026-04-09T21:16:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-5446"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5446"
},
{
"type": "REPORT",
"url": "https://github.com/wolfSSL/wolfssl/pull/10111"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
},
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-5446"
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…