{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-81019 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-81019 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81019 is a high-severity vulnerability in wolfSSL Inc. wolfProvider, published on 28 Aug 2026."},"fix_prompt":"Check this codebase for CVE-2026-81019 and fix it if it is affected.\n\nWhat it is: CVE-2026-81019 is a high-severity vulnerability in wolfSSL Inc. wolfProvider, published on 28 Aug 2026. \nExploitation: There is no known exploitation of CVE-2026-81019 in the wild and no public exploit code.\n\nAffected product: wolfSSL Inc. wolfProvider. 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-81019/ (Markdown: https://insights.sbomify.com/CVE-2026-81019/index.md)","id":"CVE-2026-81019","markdown":"https://insights.sbomify.com/CVE-2026-81019/index.md","name":"CVE-2026-81019","record":{"aliases":["GHSA-pq4j-x8cj-rwpc"],"analysis":null,"analysis_generated_by":null,"assigner":"wolfSSL","cpe":[{"product":"wolfprovider","vendor":"wolfssl"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-323","name":"Reusing a Nonce, Key Pair in Encryption"}],"description":"wolfProvider before 1.2.2 generates the 8-byte explicit AES-GCM nonce once when the TLS write key is set and never increments it per record. As a result every TLS 1.2 and DTLS 1.2 AES-GCM record within a connection is encrypted under an identical key and nonce pair. Reusing a GCM key and nonce discloses the keystream (the XOR of two ciphertexts equals the XOR of their plaintexts, so one known record recovers the others) and leaks the GHASH authentication key, enabling authentication tag forgery. AES-CCM, TLS 1.3, and non-TLS use of the cipher are not affected.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"wolfProvider reuses the AES-GCM nonce on every TLS 1.2 / DTLS 1.2 record","id":"CVE-2026-81019","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"wolfEngine reuses the AES-GCM nonce on every TLS 1.2 / DTLS 1.2 record","id":"CVE-2026-81020"},"packages":[],"prev":{"headline":"platform/x86: think-lmi: Free system certificate signatures","id":"CVE-2026-81018"},"products":["wolfProvider"],"published":"2026-08-28","related":[],"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":"total"},"state":"PUBLISHED","updated":"2026-08-28","vendors":["wolfSSL Inc."]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-81019/"}