CVE-2026-0819

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: LOW) published 2026-03-19. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A stack buffer overflow vulnerability exists in wolfSSL's PKCS7 SignedData encoding functionality. In wc_PKCS7_BuildSignedAttributes(), when adding custom signed attributes, the code passes an incorrect capacity value (esd->signedAttribsCount) to EncodeAttributes() instead of the remaining available space in the fixed-size signedAttribs[7] array. When an application sets pkcs7->signedAttribsSz to a value greater than MAX_SIGNED_ATTRIBS_SZ (default 7) minus the number of default attributes already added, EncodeAttributes() writes beyond the array bounds, causing stack memory corruption. In WOLFSSL_SMALL_STACK builds, this becomes heap corruption. Exploitation requires an application that allows untrusted input to control the signedAttribs array size when calling wc_PKCS7_EncodeSignedData() or related signing functions.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
1.1%
KEV
Not listed

Published

March 19, 2026

Last Modified

April 29, 2026

References (1)

Vendor Advisories for CVE-2026-0819(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 28× 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.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-08 15:15 UTCEPSS rescore
  8. 2026-07-08 15:15 UTCEPSS rescore
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-01 15:06 UTCEPSS rescore
  14. 2026-07-01 15:06 UTCEPSS rescore
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-27 03:08 UTCEPSS rescore
  20. 2026-06-24 14:05 UTCEPSS rescore
  21. 2026-06-23 21:32 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-21 01:59 UTCEPSS rescore
  25. 2026-06-21 01:59 UTCEPSS rescore
Show 69 more
  1. 2026-06-18 17:52 UTCEPSS rescore
  2. 2026-06-17 17:53 UTCEPSS rescore
  3. 2026-06-16 17:52 UTCEPSS rescore
  4. 2026-06-15 17:48 UTCEPSS rescore
  5. 2026-06-14 23:18 UTCEPSS rescore
  6. 2026-06-13 23:00 UTCEPSS rescore
  7. 2026-06-13 23:00 UTCEPSS rescore
  8. 2026-06-12 23:12 UTCEPSS rescore
  9. 2026-06-11 23:44 UTCEG score recompute
  10. 2026-06-11 23:44 UTCGHSA enrichment
  11. 2026-06-11 14:00 UTCEPSS rescore
  12. 2026-06-10 22:18 UTCEPSS rescore
  13. 2026-06-10 17:41 UTCEG score recompute
  14. 2026-06-10 17:41 UTCGHSA enrichment
  15. 2026-06-10 13:22 UTCEPSS rescore
  16. 2026-06-10 05:44 UTCEG score recompute
  17. 2026-06-10 05:44 UTCGHSA enrichment
  18. 2026-06-09 16:30 UTCEG score recompute
  19. 2026-06-09 16:30 UTCGHSA enrichment
  20. 2026-06-08 14:17 UTCEPSS rescore
  21. 2026-06-08 14:17 UTCEPSS rescore
  22. 2026-06-08 01:50 UTCEG score recompute
  23. 2026-06-08 01:50 UTCGHSA enrichment
  24. 2026-06-07 15:25 UTCEPSS rescore
  25. 2026-06-07 15:24 UTCEPSS rescore
  26. 2026-06-07 14:22 UTCEG score recompute
  27. 2026-06-07 14:22 UTCGHSA enrichment
  28. 2026-06-06 13:47 UTCEPSS rescore
  29. 2026-06-06 13:47 UTCEPSS rescore
  30. 2026-06-06 13:47 UTCEPSS rescore
  31. 2026-06-05 22:47 UTCEPSS rescore
  32. 2026-06-05 06:10 UTCEPSS rescore
  33. 2026-06-05 06:10 UTCEPSS rescore
  34. 2026-06-04 13:12 UTCEPSS rescore
  35. 2026-06-04 13:12 UTCEPSS rescore
  36. 2026-06-04 13:12 UTCEPSS rescore
  37. 2026-06-02 20:13 UTCEPSS rescore
  38. 2026-06-02 20:13 UTCEPSS rescore
  39. 2026-06-01 13:51 UTCEPSS rescore
  40. 2026-06-01 13:51 UTCEPSS rescore
  41. 2026-06-01 13:51 UTCEPSS rescore
  42. 2026-05-31 22:30 UTCEPSS rescore
  43. 2026-05-31 22:30 UTCEPSS rescore
  44. 2026-05-31 00:16 UTCEPSS rescore
  45. 2026-05-31 00:16 UTCEPSS rescore
  46. 2026-05-31 00:16 UTCEPSS rescore
  47. 2026-05-29 13:44 UTCEPSS rescore
  48. 2026-05-29 13:44 UTCEPSS rescore
  49. 2026-05-28 13:44 UTCEPSS rescore
  50. 2026-05-28 13:44 UTCEPSS rescore
  51. 2026-05-28 13:44 UTCEPSS rescore
  52. 2026-05-27 13:40 UTCEPSS rescore
  53. 2026-05-27 13:40 UTCEPSS rescore
  54. 2026-05-27 13:40 UTCEPSS rescore
  55. 2026-05-26 13:44 UTCEPSS rescore
  56. 2026-05-26 13:44 UTCEPSS rescore
  57. 2026-05-26 07:18 UTCEPSS rescore
  58. 2026-05-26 07:18 UTCEPSS rescore
  59. 2026-05-26 07:18 UTCEPSS rescore
  60. 2026-05-22 21:16 UTCEPSS rescore
  61. 2026-05-20 22:38 UTCEPSS rescore
  62. 2026-05-20 22:37 UTCEPSS rescore
  63. 2026-05-20 22:37 UTCEPSS rescore
  64. 2026-05-20 20:56 UTCEG score recompute
  65. 2026-05-20 20:56 UTCGHSA enrichment
  66. 2026-05-20 11:22 UTCEPSS rescore
  67. 2026-05-20 11:21 UTCEPSS rescore
  68. 2026-05-20 11:21 UTCEPSS rescore
  69. 2026-05-18 21:31 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-0819?
CVE-2026-0819 is a high vulnerability published on March 19, 2026. A stack buffer overflow vulnerability exists in wolfSSL's PKCS7 SignedData encoding functionality. In wcPKCS7BuildSignedAttributes(), when adding custom signed attributes, the code passes an incorrect capacity value (esd->signedAttribsCount) to EncodeAttributes() instead of the remaining available…
When was CVE-2026-0819 disclosed?
CVE-2026-0819 was first published in the National Vulnerability Database on March 19, 2026, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0819 actively exploited?
CVE-2026-0819 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-0819?
CVE-2026-0819 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-0819?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0819, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-0819

Explore →

Is Your Infrastructure Affected by CVE-2026-0819?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs