Home/CVE/A flaw was found in libgnutls. A remote attacker, by sending an extremely short premaster secret during an RSA key excha
CVE
CVE-2026-5260
A flaw was found in libgnutls. A remote attacker, by sending an extremely short premaster secret during an RSA key excha
A flaw was found in libgnutls. A remote attacker, by sending an extremely short premaster secret during an RSA key exchange to a server using an RSA key backed by a PKCS#11 token, could trigger a short heap overread. This memory corruption vulnerability could lead to information disclosure.
HIGH · CVSS 8.2
EPSS 0.00232
Schedule remediation
- SSVC automatable: yes - attacks can be scripted at scale
- CVSS base score ≥ 7.0
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-5260, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
1Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
▤ Build a SIEM detection for these techniques⬡
Weakness Classification
📦
Fixed versions by distribution
27The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
alpine edgegnutls fixed in 3.8.13-r0
alpine v3.20gnutls fixed in 3.8.13-r0
oracle allgnutls open
oracle allgnutls-c++ fixed in 0:3.6.16-8.el8_10.6
oracle allgnutls-dane fixed in 0:3.6.16-8.el8_10.6
oracle allgnutls-devel fixed in 0:3.6.16-8.el8_10.6
oracle allgnutls-utils open
rhel 8gnutls fixed in 0:3.6.16-8.el8_10.6
rhel 8gnutls-c++ fixed in 0:3.6.16-8.el8_10.6
rhel 8gnutls-dane fixed in 0:3.6.16-8.el8_10.6
rhel 8gnutls-devel open
rhel 8gnutls-utils open
rhel 9gnutls open
rhel 9gnutls-c++ fixed in 0:3.8.10-4.el9_8
rhel 9gnutls-dane open
rhel 9gnutls-devel open
rhel 9gnutls-utils open
suse sle15gnutls fixed in 0:3.8.3-150600.4.20.1
suse sle15gnutls-guile fixed in 0:3.7.3-150400.4.59.1
suse sle15libgnutls-devel fixed in 0:3.8.3-150600.4.20.1
suse sle15libgnutls30 fixed in 0:3.7.3-150400.4.59.1
suse sle15libgnutls30-32bit fixed in 0:3.7.3-150400.4.59.1
suse sle15libgnutls30-hmac fixed in 0:3.7.3-150400.4.59.1
suse sle15libgnutls30-hmac-32bit fixed in 0:3.7.3-150400.4.59.1
suse sle15libgnutlsxx-devel fixed in 0:3.7.3-150400.4.59.1
suse sle15libgnutlsxx28 fixed in 0:3.7.3-150400.4.59.1
suse sle15libgnutlsxx30 fixed in 0:3.8.3-150600.4.20.1
▣
Scoring & Timeline
8.2
HIGH · CVSS v3.1 · [email protected]
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Technical impact
partial
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
⚑
Vendor Advisories
14msrcCVE-2026-5260
suse-csafSUSE-SU-2026:2115-1
suse-csafSUSE-SU-2026:2087-1
suse-csafSUSE-SU-2026:21784-1
suse-csafSUSE-SU-2026:21867-1
🔗
References & Sources
2Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.