CVE-2026-57826 json
An issue was discovered in openHiTLS 0.2.0 through 0.3.2.
published 2mo ago modified 2d ago also EUVD-2026-61278
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- github.com/openHiTLS/openHiTLS@4355cdf commit
- github.com/openHiTLS/openHiTLS@2d3b221 commit
- gitcode.com/openHiTLS/openhitls#1399 pull request
- gitcode.com/openHiTLS/openhitls#1657 pull request
Is CVE-2026-57826 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2mo ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N |
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N |
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
- github.com /openHiTLS/openHiTLS/commit/4355cdf5b043d5b9ef698f8f57860f77f8e92561
- github.com /openHiTLS/openHiTLS/commit/2d3b221d113b452bc197012b185978b8314ee8a4
- gitcode.com /openHiTLS/openhitls/pull/1399
- gitcode.com /openHiTLS/openhitls/pull/1657
- github.com /openHiTLS/openHiTLS/compare/openhitls-0.3.2...openhitls-0.3.3
- openhitls.net /zh/support/HTLS-2026-001.html
Sources
- CVE List CVE-2026-57826
- NVD CVE-2026-57826
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.