CVE-2026-84782
waiting for further signalsZero needs more public information before it can validate it.GHSA-6w84-hw79-7wgf ↗EUVD-2026-89013 ↗
description
OpenSSL DTLS handshake processing can read beyond a message buffer during retransmission, potentially disclosing heap data to the connected peer or causing a denial of service. The condition requires a fragmented handshake write to be paused because the transport cannot accept more data while retransmission is triggered before the write resumes.
mitigation
Update OpenSSL to a release containing the upstream DTLS retransmission fix; the evidence does not provide a fixed version number. Disable DTLS where feasible until the update is deployed, or limit DTLS access to trusted peers.
fixed in 4.0.3, 3.6.5, 3.5.9, 3.4.8, 3.0.23, 1.1.1zj, 1.0.2zs
outcome
No artifact: an exploit or check was attempted but could not be produced at this moment.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-09-29 15:32Zthehackernews: trigger signal, started the run
- 2026-09-29 15:32Zcve.org record for CVE-2026-84782
- 2026-10-02 00:27ZOpenSSL Fixes High-Severity DTLS Flaw That Can Leak Heap Memory Unencrypted
this entry in the feed
GET /api/v1/feed/CVE-2026-84782
{ "etk_id": "ETK-2026-545", "cve_id": "CVE-2026-84782", "display_id": "CVE-2026-84782", "ghsa_id": "GHSA-6w84-hw79-7wgf", "euvd_id": "EUVD-2026-89013", "status": "published", "anchor_state": "anchored", "title": "OpenSSL DTLS retransmission out-of-bounds read", "summary": "OpenSSL DTLS handshake processing can read beyond a message buffer during retransmission, potentially disclosing heap data to the connected peer or causing a denial of service. The condition requires a fragmented handshake write to be paused because the transport cannot accept more data while retransmission is triggered before the write resumes.", "mitigation": "Update OpenSSL to a release containing the upstream DTLS retransmission fix; the evidence does not provide a fixed version number. Disable DTLS where feasible until the update is deployed, or limit DTLS access to trusted peers.", "vendor": "openssl", "product": "OpenSSL", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 4.0.0, < 4.0.3", ">= 3.6.0, < 3.6.5", ">= 3.5.0, < 3.5.9", ">= 3.4.0, < 3.4.8", ">= 3.0.0, < 3.0.23", ">= 1.1.1, < 1.1.1zj", ">= 1.0.2, < 1.0.2zs" ], "ecosystem": null, "fixed_versions": [ "4.0.3", "3.6.5", "3.5.9", "3.4.8", "3.0.23", "1.1.1zj", "1.0.2zs" ], "package_name": "OpenSSL", "purl": null } ], "cwes": [ 125 ], "cvss_score": 8.2, "cvss_src": "nvd", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H", "epss_score": 0.0039, "epss_percentile": 0.3173, "epss_asof": "2026-10-20", "automation": "deterministic", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 18.073522316666665, "t0_at": "2026-09-29T15:32:23.605000+00:00", "signals": { "trigger_signal": { "at": "2026-09-29T15:32:23.605000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-09-29T15:32:23.605000+00:00", "url": "https://thehackernews.com/2026/09/openssl-fixes-high-severity-dtls-flaw.html" } } }
published 2026-10-04 08:43Z
last change 2026-10-21 05:31Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.