CVE-2026-6731

HIGHNVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory published 2026-06-25. 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.

X.509 name constraint bypass via the Subject Common Name when treated as a DNS-type name. A certificate whose Subject CN violates an issuing CA's DNS name constraints could be accepted.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
2.5%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 27, 2026

Advisory Details (2)

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

wolfSSL Security Vulnerabilities | Documentation - wolfSSL

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

CN constraints fix

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

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

Vendor Advisories for CVE-2026-6731(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 30× in last 7d / 48× 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 21:53 UTCEG score recompute
  2. 2026-07-06 21:53 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 08:44 UTCEG score recompute
  6. 2026-07-06 08:44 UTCGHSA enrichment
  7. 2026-07-05 19:34 UTCEG score recompute
  8. 2026-07-05 19:34 UTCGHSA enrichment
  9. 2026-07-05 06:27 UTCEG score recompute
  10. 2026-07-05 06:27 UTCGHSA enrichment
  11. 2026-07-04 17:19 UTCEG score recompute
  12. 2026-07-04 17:18 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-04 04:10 UTCEG score recompute
  16. 2026-07-04 04:10 UTCGHSA enrichment
  17. 2026-07-03 15:02 UTCEG score recompute
  18. 2026-07-03 15:01 UTCGHSA enrichment
  19. 2026-07-03 01:54 UTCEG score recompute
  20. 2026-07-03 01:53 UTCGHSA enrichment
  21. 2026-07-02 12:47 UTCEG score recompute
  22. 2026-07-02 12:46 UTCGHSA enrichment
  23. 2026-07-01 23:39 UTCEG score recompute
  24. 2026-07-01 23:39 UTCGHSA enrichment
  25. 2026-07-01 10:32 UTCEG score recompute
Show 23 more
  1. 2026-07-01 10:31 UTCGHSA enrichment
  2. 2026-06-30 21:22 UTCEG score recompute
  3. 2026-06-30 21:22 UTCGHSA enrichment
  4. 2026-06-30 08:13 UTCEG score recompute
  5. 2026-06-30 08:13 UTCGHSA enrichment
  6. 2026-06-29 19:05 UTCEG score recompute
  7. 2026-06-29 19:05 UTCGHSA enrichment
  8. 2026-06-29 14:06 UTCEPSS rescore
  9. 2026-06-29 05:58 UTCEG score recompute
  10. 2026-06-29 05:58 UTCGHSA enrichment
  11. 2026-06-28 16:48 UTCEG score recompute▲ 1.50
  12. 2026-06-28 16:48 UTCGHSA enrichment
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-27 21:42 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  16. 2026-06-27 16:16 UTCEG score recompute
  17. 2026-06-27 16:16 UTCGHSA enrichment
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-26 15:44 UTCEG score recompute▲ 6.00
  20. 2026-06-26 15:44 UTCGHSA enrichment
  21. 2026-06-26 15:40 UTCNVD updateCVSS v3 → 6 · CVSS v4 → 6
  22. 2026-06-25 21:46 UTCEG score recompute
  23. 2026-06-25 21:46 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-6731?
CVE-2026-6731 is a high vulnerability published on June 25, 2026. X.509 name constraint bypass via the Subject Common Name when treated as a DNS-type name. A certificate whose Subject CN violates an issuing CA's DNS name constraints could be accepted.
When was CVE-2026-6731 disclosed?
CVE-2026-6731 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-6731 actively exploited?
CVE-2026-6731 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-6731?
CVE-2026-6731 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-6731?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6731, 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-6731

Explore →

Is Your Infrastructure Affected by CVE-2026-6731?

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

Start Free Scan →Browse All CVEs