Koffei

CVE-2026-75806

🟡 Low

OpenSSL · 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

CVSS (Koffei note)
5.3
CVSS (v3.1, CVE List)
5.3
EPSS (2026-11-18)
1.220%
69.27th percentile

Exploitation

No (SSVC: none, CISA-ADP 2026-09-29); not in KEV. Not in the 0day "In the Wild" sheet (checked 18/11/2026). cyberveille RSS: checked 18/11/2026 (feed 19/10 to 17/11/2026), no result (automated enrichment)

Timeline

  1. 29/09/2026CVE record published (CVE List)
  2. 18/11/2026CERT-FR relays Oracle's off-cycle November update for six product lines

Risk

5.3 Medium (v3.1, CISA-ADP) — AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, EPSS 1.220%, 69.18th percentile, scored 2026-11-17 (CWE-1284: A single unauthenticated datagram with an encrypted fragment shorter than the AEAD IV+tag overhead can tear down an established DTLS 1.2 AEAD association (DoS). No memory-safety or confidentiality impact; outside FIPS boundary.)

Fix

Yes — Oracle Database Server: Oracle cspunov2026 (17/11/2026) ; component fix per record: 4.0.3, 3.6.5, 3.5.9, 3.4.8, 3.0.23, 1.1.1zj

Official description

Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

CWE-1284