{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-3229 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-3229 is a low-severity vulnerability in Wolfssl Wolfssl, published on 19 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-3229 and fix it if it is affected.\n\nWhat it is: CVE-2026-3229 is a low-severity vulnerability in Wolfssl Wolfssl, published on 19 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-3229 in the wild and no public exploit code.\n\nAffected product: Wolfssl Wolfssl. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-3229/ (Markdown: https://insights.sbomify.com/CVE-2026-3229/index.md)","id":"CVE-2026-3229","markdown":"https://insights.sbomify.com/CVE-2026-3229/index.md","name":"CVE-2026-3229","record":{"aliases":["DEBIAN-CVE-2026-3229","GHSA-6p64-86qj-33gc","JLSEC-2026-703","UBUNTU-CVE-2026-3229"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"wolfSSL library","requires_auth":"none","summary":"An integer overflow in wolfSSL certificate chain allocation can cause heap corruption and potential code execution if the application context is compromised.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"wolfSSL","cpe":[{"product":"wolfssl","vendor":"wolfssl"}],"cvss":{"score":1.2,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/U:Green","version":"4.0"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Integer Overflow in Certificate Chain Allocation","id":"CVE-2026-3229","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wolfssl:wolfssl","products":["wolfssl:wolfssl"],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Improper key_share validation in TLS 1.3 HelloRetryRequest","id":"CVE-2026-3230"},"packages":[],"prev":{"headline":"Cross-site scripting in NextScripts: Social Networks Auto-Poster","id":"CVE-2026-3228"},"products":["wolfSSL"],"published":"2026-03-19","related":[{"cvss_score":10,"headline":"Buffer overread in domain name matching","id":"CVE-2024-5991","kev_date_added":null,"published":"2024-08-27"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2021-37155","kev_date_added":null,"published":"2021-07-21"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-36177","kev_date_added":null,"published":"2021-01-06"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2014-2896","kev_date_added":null,"published":"2020-01-28"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2014-2897","kev_date_added":null,"published":"2020-01-28"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2014-2898","kev_date_added":null,"published":"2020-01-28"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-16748","kev_date_added":null,"published":"2019-09-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-20","vendors":["wofSSL"]},"summary":"An integer overflow in wolfSSL certificate chain allocation can cause heap corruption and potential code execution if the application context is compromised.","url":"https://insights.sbomify.com/CVE-2026-3229/"}