CVE-2026-6681

MEDIUMNVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory (severity: LOW) published 2026-06-25. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

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

The PKCS#7 decode path ignores the caller-supplied output buffer size (outputSz), allowing decoded content to be written past the bounds of the provided buffer. This affects wolfSSL 5.9.0 and earlier and was fixed in the 5.9.1 release.

CVSS v3
5.3
EG Score
5.3(high)
EPSS
17.0%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 27, 2026

Advisory Details (2)

Auto-updated Jun 27, 2026
Patch available. Sources: github_pr.
generic Patch Available

wolfSSL Security Vulnerabilities | Documentation - wolfSSL

https://www.wolfssl.com/docs/security-vulnerabilities/
github_pr

Additional fixes

Fix merged in wolfSSL/wolfssl PR #10116 on 2026-04-07 — awaiting tagged release

https://github.com/wolfSSL/wolfssl/pull/10116

Vendor Advisories for CVE-2026-6681(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 24× in last 7d / 36× 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-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 11:14 UTCEG score recompute
  4. 2026-07-06 11:14 UTCGHSA enrichment
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 12:30 UTCEG score recompute
  8. 2026-07-05 12:30 UTCGHSA enrichment
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 14:03 UTCEG score recompute
  12. 2026-07-04 14:03 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 15:26 UTCEG score recompute
  16. 2026-07-03 15:26 UTCGHSA enrichment
  17. 2026-07-02 16:59 UTCEG score recompute
  18. 2026-07-02 16:59 UTCGHSA enrichment
  19. 2026-07-01 18:31 UTCEG score recompute
  20. 2026-07-01 18:31 UTCGHSA enrichment
  21. 2026-07-01 15:07 UTCEPSS rescore
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 20:03 UTCEG score recompute
  24. 2026-06-30 20:03 UTCGHSA enrichment
  25. 2026-06-29 21:35 UTCEG score recompute▲ 4.30
Show 11 more
  1. 2026-06-29 21:35 UTCGHSA enrichment
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-27 21:42 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-26 15:44 UTCEG score recompute▲ 1.00
  8. 2026-06-26 15:44 UTCGHSA enrichment
  9. 2026-06-26 15:40 UTCNVD updateCVSS v3 → 1 · CVSS v4 → 1
  10. 2026-06-25 21:46 UTCEG score recompute
  11. 2026-06-25 21:46 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-6681?
CVE-2026-6681 is a medium vulnerability published on June 25, 2026. The PKCS#7 decode path ignores the caller-supplied output buffer size (outputSz), allowing decoded content to be written past the bounds of the provided buffer. This affects wolfSSL 5.9.0 and earlier and was fixed in the 5.9.1 release.
When was CVE-2026-6681 disclosed?
CVE-2026-6681 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6681 actively exploited?
CVE-2026-6681 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-6681?
CVE-2026-6681 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-6681?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6681, 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-6681

Explore →

Is Your Infrastructure Affected by CVE-2026-6681?

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

Start Free Scan →Browse All CVEs