JLSEC-2026-737
- Source
- https://github.com/JuliaLang/SecurityAdvisories.jl/blob/main/advisories/published/2026/JLSEC-2026-737.md
- Import Source
- https://github.com/JuliaLang/SecurityAdvisories.jl/tree/generated/osv/2026/JLSEC-2026-737.json
- JSON Data
- https://api.osv.dev/v1/vulns/JLSEC-2026-737
- Upstream
- Published
- 2026-07-14T21:41:35.775Z
- Modified
- 2026-07-18T00:02:21.959341004Z
- Severity
-
- 6.5 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N CVSS Calculator
- 6.0 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X CVSS Calculator
- Summary
- TLS 1.3 post-handshake authentication (PHA) issue where a server could accept a client's Finished...
- Details
-
TLS 1.3 post-handshake authentication (PHA) issue where a server could accept a client's Finished message without the client having sent a Certificate and CertificateVerify. The post-handshake-auth exemption that allows an empty/absent peer certificate was only intended for the initial handshake, but it was also being applied while a post-handshake CertificateRequest was still outstanding. The check is now scoped to the initial handshake only: on the server, once a post-handshake CertificateRequest has been sent (certReqCtx is set), a peer certificate and a valid CertificateVerify are required again before the Finished is accepted, with empty-certificate handling following the configured verify mode (FAILIFNOPEERCERT) just as during first-handshake client authentication. Only affects TLS 1.3 servers built with post-handshake authentication support (WOLFSSLPOSTHANDSHAKEAUTH / --enable-postauth, included in --enable-all) that enable WOLFSSLVERIFYPOSTHANDSHAKE and request a client certificate after the handshake via wolfSSLrequestcertificate(). Clients, and servers that do not use post-handshake authentication, are unaffected.
- Database specific
{ "sources": [ { "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-55962", "published": "2026-06-25T22:17:02.260Z", "html_url": "https://nvd.nist.gov/vuln/detail/CVE-2026-55962", "modified": "2026-06-27T19:57:59.510Z", "imported": "2026-07-17T22:33:33.117Z", "id": "CVE-2026-55962", "database_specific": { "status": "Analyzed" } }, { "html_url": "https://github.com/advisories/GHSA-gq94-hf88-g4wv", "published": "2026-06-26T00:32:06Z", "url": "https://api.github.com/advisories/GHSA-gq94-hf88-g4wv", "imported": "2026-07-17T22:33:33.324Z", "id": "GHSA-gq94-hf88-g4wv", "modified": "2026-06-27T21:31:34Z" }, { "url": "https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2026-39575", "html_url": "https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-39575", "modified": "2026-06-26T10:31:12Z", "imported": "2026-07-17T22:33:43.200Z", "published": "2026-06-25T21:12:38Z", "id": "EUVD-2026-39575" } ], "license": "CC-BY-4.0" }- References