An issue was discovered in openHiTLS 0.2.0 through 0.3.2. In the X.509 certificate chain verification, the basic constraints extension and CA flag processing of intermediate CAs are only verified for v3 certificates, and v1/v2 certificates are ignored.
CVE-2026-57826
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-18. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 59(Track)EG Risk 59/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 computedSeverity98% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 24%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 19, 2026
Advisory Details (6)
Auto-updated Aug 19, 2026Comparing openhitls-0.3.2...openhitls-0.3.3 · openHiTLS/openHiTLS · GitHub
https://github.com/openHiTLS/openHiTLS/compare/openhitls-0.3.2...openhitls-0.3.3commit 4355cdf5b043 (openHiTLS/openHiTLS)
Patch available: openHiTLS/openHiTLS openhitls-0.3.3 (contains commit 4355cdf5b043)
https://github.com/openHiTLS/openHiTLS/commit/4355cdf5b043d5b9ef698f8f57860f77f8e92561commit 2d3b221d113b (openHiTLS/openHiTLS)
Fix landed in openHiTLS/openHiTLS commit 2d3b221d113b — awaiting tagged release
https://github.com/openHiTLS/openHiTLS/commit/2d3b221d113b452bc197012b185978b8314ee8a4Vendor Advisories for CVE-2026-57826(1)
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 20× in last 7d / 20× 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.
- 2026-08-21 05:39 UTCGHSA enrichment
- 2026-08-21 01:21 UTCEG score recompute
- 2026-08-21 01:21 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 21:04 UTCGHSA enrichment
- 2026-08-20 16:47 UTCGHSA enrichment
- 2026-08-20 12:30 UTCGHSA enrichment
- 2026-08-20 08:13 UTCGHSA enrichment
- 2026-08-20 03:56 UTCGHSA enrichment
- 2026-08-19 23:39 UTCEG score recompute
- 2026-08-19 23:39 UTCGHSA enrichment
- 2026-08-19 19:21 UTCGHSA enrichment
- 2026-08-19 18:38 UTCEG score recompute▲ 9.80
- 2026-08-19 18:38 UTCGHSA enrichment
- 2026-08-19 18:37 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 21:36 UTCGHSA enrichment
- 2026-08-18 20:22 UTCNVD update
- 2026-08-18 20:10 UTCEG score recompute
- 2026-08-18 20:08 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-57826?
When was CVE-2026-57826 disclosed?
Is CVE-2026-57826 actively exploited?
What is the CVSS score of CVE-2026-57826?
How do I remediate CVE-2026-57826?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-57826
Is Your Infrastructure Affected by CVE-2026-57826?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.