An integer overflow vulnerability existed in the static function wolfssl_add_to_chain, that caused heap corruption when certificate data was written out of bounds of an insufficiently sized certificate buffer. wolfssl_add_to_chain is called by these API: wolfSSL_CTX_add_extra_chain_cert, wolfSSL_CTX_add1_chain_cert, wolfSSL_add0_chain_cert. These API are enabled for 3rd party compatibility features: enable-opensslall, enable-opensslextra, enable-lighty, enable-stunnel, enable-nginx, enable-haproxy. This issue is not remotely exploitable, and would require that the application context loading certificates is compromised.
CVE-2026-3229
Score 5.5 from GitHub Security Advisory (severity: LOW) published 2026-03-19. the CNA's CVSS baseline 1.2; sources differ by 4.3.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(medium)
- EG Risk
- 25(Track)EG Risk 25/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity55% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 0%
- KEV
- Not listed
Published
March 19, 2026
Last Modified
June 17, 2026
References (1)
- facts@wolfsslhttps://github.com/wolfSSL/wolfssl/pull/9827
Vendor Advisories for CVE-2026-3229(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 12:51 UTCEG score recompute
- 2026-07-27 12:51 UTCGHSA enrichment
- 2026-07-27 12:50 UTCOSV refresh
Frequently asked(5)
What is CVE-2026-3229?
When was CVE-2026-3229 disclosed?
Is CVE-2026-3229 actively exploited?
What is the CVSS score of CVE-2026-3229?
How do I remediate CVE-2026-3229?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-3229
Is Your Infrastructure Affected by CVE-2026-3229?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.