Direct Vulnerabilities

Known vulnerabilities in the gnutls28 package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free
VulnerabilityVulnerable Version
  • L
CVE-2026-95184

*
  • L
CVE-2026-67693

*
  • L
CVE-2026-88648

*
  • L
CVE-2026-95210

*
  • L
CVE-2026-95209

*
  • L
CVE-2026-88647

*
  • H
Improper Handling of Case Sensitivity

<3.8.13-1
  • L
Information Exposure

<3.8.13-1
  • H
Improper Handling of Length Parameter Inconsistency

<3.8.13-1
  • H
Undefined Behavior for Input to API

<3.8.13-1
  • C
Integer Underflow

<3.8.13-1
  • H
Improper Certificate Validation

<3.8.13-1
  • H
Improper Validation of Specified Quantity in Input

<3.8.13-1
  • C
Improper Null Termination

<3.8.13-1
  • H
Improper Certificate Validation

<3.8.13-1
  • L
Incorrect Behavior Order: Early Validation

<3.8.13-1
  • M
Expired Pointer Dereference

<3.8.13-1
  • M
Off-by-one Error

<3.8.13-1
  • H
Improper Validation of Specified Quantity in Input

<3.8.13-1
  • M
Algorithmic Complexity

<3.8.12-1
  • H
NULL Pointer Dereference

<3.8.12-1
  • M
Stack-based Buffer Overflow

<3.8.11-3
  • M
NULL Pointer Dereference

<3.7.3-2
  • C
Use After Free

<3.7.1-1
  • M
Improper Data Handling

<3.3.15-1
  • M
Cryptographic Issues

<3.3.8-4
  • H
Out-of-bounds Read

<3.5.8-1
  • M
Cryptographic Issues

<3.0.22-3
  • L
Cryptographic Issues

<3.0.22-3
  • H
Double Free

<3.6.7-2
  • M
Information Exposure

<3.8.2-1
  • M
Use of a Broken or Risky Cryptographic Algorithm

<3.5.19-1
  • M
Use of a Broken or Risky Cryptographic Algorithm

<3.5.19-1
  • H
Heap-based Buffer Overflow

<3.8.9-3
  • L
Use of a Broken or Risky Cryptographic Algorithm

<3.8.4-2
  • H
Resource Management Errors

<3.0.14-1
  • H
Information Exposure

<3.7.8-5
  • H
Double Free

<3.8.9-3
  • H
Cryptographic Issues

<3.0.17-2
  • M
Use of a Broken or Risky Cryptographic Algorithm

<3.5.19-1
  • M
NULL Pointer Dereference

<3.8.9-3
  • H
Improper Verification of Cryptographic Signature

<3.8.3-1
  • M
Information Exposure

<3.6.5-2
  • C
Out-of-Bounds

<3.5.8-1
  • H
Access of Uninitialized Pointer

<3.6.7-2
  • H
Use of a Broken or Risky Cryptographic Algorithm

<3.6.14-1
  • H
CVE-2015-3308

<3.3.8-7
  • H
Information Exposure

<3.8.3-1
  • M
Out-of-Bounds

<3.2.15-1
  • H
Improper Certificate Validation

<3.3.8-6
  • C
Double Free

<3.5.8-1
  • H
NULL Pointer Dereference

<3.5.8-6
  • M
Access Restriction Bypass

<3.2.11-1
  • M
Algorithmic Complexity

<3.8.9-2
  • H
Out-of-bounds Write

<3.6.15-1
  • L
Improper Input Validation

*
  • H
Access Restriction Bypass

<3.5.3-4
  • M
Cryptographic Issues

<3.2.11-2
  • C
Out-of-Bounds

<3.5.8-1
  • M
Cryptographic Issues

<3.0.11-1
  • H
Double Free

<3.7.7-1
  • C
Use After Free

<3.7.1-1
  • L
Uncaught Exception

<3.8.4-2
  • H
Use of a Broken or Risky Cryptographic Algorithm

<3.6.13-2
  • M
Improper Certificate Validation

<3.8.9-3
  • H
Improper Input Validation

<3.4.13-1
  • H
Out-of-bounds Write

<3.5.8-4
  • M
CVE-2015-6251

<3.3.17-1
  • L
Cryptographic Issues

<3.3.8-5
  • M
CVE-2014-3465

<3.2.10-1