ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-75806

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 ma

Published Sep 29, 2026 · catalog updated Oct 26, 2026 · Issue summary: An established

Last checked Oct 26, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-75806. EPSS is 1.10%. Act only if a listed version of Issue summary: An established is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Issue summary: An established).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
1.10%
Remediation
Advisory link
Affected products
Debian:12 openssl · Debian:13 openssl · Debian:14 openssl

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Debian:12 openssl0 → 3.0.22-1~deb12u2
  • Debian:13 openssl0 → 3.5.7-1~deb13u3
  • Debian:14 openssl0 → 3.6.5-1

How to fix CVE-2026-75806

  • Upgrade

    CVE-2026-75806 lists a fix boundary at 3.0.22-1~deb12u2. Compare the installed build with that boundary before you change production.

  • Version check

    Fixed in 3.0.22-1~deb12u2 · 2 other ranges on the advisory

  • Advisory

    Open the cve_org record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-75806. EPSS is 1.10%. Act only if a listed version of Issue summary: An established is installed.

Which versions are affected?

Compare what you have installed with 0 → 3.0.22-1~deb12u2, 0 → 3.5.7-1~deb13u3, 0 → 3.6.5-1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 1.10%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Debian security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Sep 29, 2026 · Trivy Vulnerability DB

    Detected

    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.

  2. Oct 26, 2026 · Trivy Vulnerability DB

    Fix available

    openssl fixed in 3.0.22-1~deb12u2; openssl fixed in 3.5.7-1~deb13u3; openssl fixed in 3.6.5-1

  3. Oct 26, 2026 · Trivy Vulnerability DB

    Fix available

    openssl fixed in 3.0.22-1~deb12u2

  4. Oct 26, 2026 · Trivy Vulnerability DB

    Fix available

    openssl fixed in 3.5.7-1~deb13u3

  5. Oct 26, 2026 · Trivy Vulnerability DB

    Fix available

    openssl fixed in 3.6.5-1

  6. Oct 26, 2026 · Trivy Vulnerability DB

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2026-75806

    Official CVE identifier

    cve.org
  • Trivy Vulnerability DBPackage advisoryDEBIAN-CVE-2026-75806

    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 data

    osv.dev

References

Freshness

Last verified in this catalog Oct 26, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgOct 26, 2026
  • Trivy Vulnerability DBOct 26, 2026