# CVE-2026-5446: wolfSSL ARIA-GCM TLS 1.2/DTLS 1.2 GCM nonce reuse

> wolfSSL reuses GCM nonces in ARIA-GCM TLS/DTLS connections, potentially allowing attackers to decrypt traffic or forge messages.

- **Severity:** Medium 6.0 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-5446, GHSA-vgv9-mv66-mpc7, JLSEC-2026-722, UBUNTU-CVE-2026-5446

## What is CVE-2026-5446?

CVE-2026-5446 is a medium-severity vulnerability in Wolfssl Wolfssl, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-323 (Reusing a Nonce, Key Pair in Encryption)

## Which versions are affected by CVE-2026-5446?

It affects 1 product.


Products: Wolfssl Wolfssl.

## How do I fix CVE-2026-5446?

Apply the vendor's patch.

## Is CVE-2026-5446 being exploited?

There is no known exploitation of CVE-2026-5446 in the wild and no public exploit code.

## Other vulnerabilities in Wolfssl Wolfssl

- [CVE-2024-5991](https://insights.sbomify.com/CVE-2024-5991/): Buffer overread in domain name matching (critical 10.0)
- [CVE-2021-37155](https://insights.sbomify.com/CVE-2021-37155/): Security feature bypass in n/a (critical 9.8)
- [CVE-2020-36177](https://insights.sbomify.com/CVE-2020-36177/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-2896](https://insights.sbomify.com/CVE-2014-2896/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-2897](https://insights.sbomify.com/CVE-2014-2897/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5446 and fix it if it is affected.

What it is: CVE-2026-5446 is a medium-severity vulnerability in Wolfssl Wolfssl, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5446 in the wild and no public exploit code.

Affected product: Wolfssl Wolfssl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5446/ (Markdown: https://insights.sbomify.com/CVE-2026-5446/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5446
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5446
- OSV: https://osv.dev/vulnerability/CVE-2026-5446

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5446/
Summaries are generated and may contain mistakes; the official description above is the record.