CVE-2026-7511

HIGHNVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory published 2026-06-26. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

PKCS7_verify signer confusion allows forged signatures, where the signer associated with a signature is not correctly bound, permitting a forged signature to be accepted.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/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 computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
6.7%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 27, 2026

Advisory Details (2)

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

wolfSSL Security Vulnerabilities | Documentation - wolfSSL

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

PKCS#7 fixes

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

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

Vendor Advisories for CVE-2026-7511(2)

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 12× in last 7d / 81× 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-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:22 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-21 15:25 UTCEPSS rescore
  7. 2026-07-21 15:25 UTCEPSS rescore
  8. 2026-07-20 17:08 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-19 02:29 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-17 02:18 UTCGHSA enrichment
  13. 2026-07-16 17:03 UTCEPSS rescore
  14. 2026-07-16 13:30 UTCGHSA enrichment
  15. 2026-07-16 00:52 UTCGHSA enrichment
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 12:19 UTCGHSA enrichment
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-14 23:47 UTCGHSA enrichment
  20. 2026-07-14 11:16 UTCGHSA enrichment
  21. 2026-07-13 22:46 UTCGHSA enrichment
  22. 2026-07-13 22:31 UTCEPSS rescore
  23. 2026-07-13 10:13 UTCGHSA enrichment
  24. 2026-07-13 06:13 UTCEPSS rescore
  25. 2026-07-12 21:43 UTCGHSA enrichment
Show 56 more
  1. 2026-07-12 09:12 UTCGHSA enrichment
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-11 20:41 UTCGHSA enrichment
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-11 08:10 UTCGHSA enrichment
  7. 2026-07-10 19:39 UTCGHSA enrichment
  8. 2026-07-10 07:08 UTCGHSA enrichment
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 18:34 UTCGHSA enrichment
  12. 2026-07-09 05:59 UTCGHSA enrichment
  13. 2026-07-08 17:24 UTCGHSA enrichment
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-08 15:16 UTCEPSS rescore
  16. 2026-07-08 04:53 UTCGHSA enrichment
  17. 2026-07-07 16:13 UTCGHSA enrichment
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-07 13:46 UTCEPSS rescore
  20. 2026-07-07 03:18 UTCGHSA enrichment
  21. 2026-07-06 16:27 UTCEPSS rescore
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-06 14:46 UTCGHSA enrichment
  24. 2026-07-06 02:23 UTCEPSS rescore
  25. 2026-07-06 02:23 UTCEPSS rescore
  26. 2026-07-06 02:16 UTCGHSA enrichment
  27. 2026-07-05 13:46 UTCGHSA enrichment
  28. 2026-07-05 02:31 UTCEPSS rescore
  29. 2026-07-05 02:30 UTCEPSS rescore
  30. 2026-07-05 01:15 UTCGHSA enrichment
  31. 2026-07-04 12:28 UTCGHSA enrichment
  32. 2026-07-04 06:31 UTCEPSS rescore
  33. 2026-07-04 06:31 UTCEPSS rescore
  34. 2026-07-03 23:57 UTCGHSA enrichment
  35. 2026-07-03 11:26 UTCGHSA enrichment
  36. 2026-07-02 22:54 UTCGHSA enrichment
  37. 2026-07-02 10:23 UTCGHSA enrichment
  38. 2026-07-01 21:51 UTCGHSA enrichment
  39. 2026-07-01 15:07 UTCEPSS rescore
  40. 2026-07-01 09:20 UTCGHSA enrichment
  41. 2026-06-30 23:22 UTCEPSS rescore
  42. 2026-06-30 20:48 UTCGHSA enrichment
  43. 2026-06-30 08:17 UTCGHSA enrichment
  44. 2026-06-29 19:46 UTCGHSA enrichment
  45. 2026-06-29 14:06 UTCEPSS rescore
  46. 2026-06-29 07:16 UTCGHSA enrichment
  47. 2026-06-28 18:45 UTCEG score recompute▲ 1.60
  48. 2026-06-28 18:45 UTCGHSA enrichment
  49. 2026-06-28 14:07 UTCEPSS rescore
  50. 2026-06-28 04:56 UTCEPSS rescore
  51. 2026-06-27 21:42 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  52. 2026-06-27 20:27 UTCGHSA enrichment
  53. 2026-06-27 03:08 UTCEPSS rescore
  54. 2026-06-26 22:09 UTCGHSA enrichment
  55. 2026-06-25 23:51 UTCEG score recompute
  56. 2026-06-25 23:50 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-7511?
CVE-2026-7511 is a high vulnerability published on June 25, 2026. PKCS7_verify signer confusion allows forged signatures, where the signer associated with a signature is not correctly bound, permitting a forged signature to be accepted.
When was CVE-2026-7511 disclosed?
CVE-2026-7511 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-7511 actively exploited?
CVE-2026-7511 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-7511?
CVE-2026-7511 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-7511?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7511, 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-7511

Explore →

Is Your Infrastructure Affected by CVE-2026-7511?

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

Start Free Scan →Browse All CVEs