Stack-based buffer overflow in libtasn1 version: v4.20.0.
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 66.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: azl3 gnutls 3.8.3-8 on Azure Linux 3.0 3.8.3-8; azl3 libtasn1 4.19.0-2 on Azure Linux 3.0 4.19.0-3; azl3 libtasn1 4.19.0-3 on Azure Linux 3.0 4.19.0-3.
Low priority for now. Upgrade to azl3 gnutls 3.8.3-8 on Azure Linux 3.0 3.8.3-8; azl3 libtasn1 4.19.0-2 on Azure Linux 3.0 4.19.0-3; azl3 libtasn1 4.19.0-3 on Azure Linux 3.0 4.19.0-3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Stack-based buffer overflow in libtasn1 version: v4.20.0. The function fails to validate the size of input data resulting in a buffer overflow in asn1_expend_octet_string.
- BDU:2026-05140
- ALSA-2026:28235
- ALSA-2026:28253
- ALSA-2026:36728
- openSUSE-SU-2026:10033-1
- openSUSE-SU-2026:20470-1
- RHSA-2026:28235
- RHSA-2026:28253
- RHSA-2026:36728
- RHSA-2026:7500
- RLSA-2026:28235
- RLSA-2026:28253
- RLSA-2026:36728
- SUSE-SU-2026:0118-1
- SUSE-SU-2026:0224-1
- SUSE-SU-2026:20051-1
- SUSE-SU-2026:20355-1
- SUSE-SU-2026:21001-1
- SUSE-SU-2026:21142-1
- Published
- Jan 7, 2026
- Updated
- Jun 17, 2026
- EPSS
- 1.2% · 67th percentile
- CWE
- CWE-787
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| gnu | libtasn1 | cpe:2.3:a:gnu:libtasn1 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- gnu libtasn14.20.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (certcc). Independent of NVD's CPE analysis and usually ahead of it.
GnuTLS libtasn1
- up to and including 4.20.0affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | libtasn1 | before 4.20.0-5.el10_2 | 4.20.0-5.el10_2 |
| AlmaLinux:10 | libtasn1-devel | before 4.20.0-5.el10_2 | 4.20.0-5.el10_2 |
| AlmaLinux:10 | libtasn1-tools | before 4.20.0-5.el10_2 | 4.20.0-5.el10_2 |
| AlmaLinux:8 | libtasn1 | before 4.13-6.el8_10 | 4.13-6.el8_10 |
| AlmaLinux:8 | libtasn1-devel | before 4.13-6.el8_10 | 4.13-6.el8_10 |
| AlmaLinux:8 | libtasn1-tools | before 4.13-6.el8_10 | 4.13-6.el8_10 |
| AlmaLinux:9 | libtasn1 | before 4.16.0-10.el9_8 | 4.16.0-10.el9_8 |
| AlmaLinux:9 | libtasn1-devel | before 4.16.0-10.el9_8 | 4.16.0-10.el9_8 |
| AlmaLinux:9 | libtasn1-tools | before 4.16.0-10.el9_8 | 4.16.0-10.el9_8 |
| Alpine:v3.20 | libtasn1 | before 4.21.0-r0 | 4.21.0-r0 |
| Debian:12 | libtasn1-6 | all versions | — |
| Debian:13 | libtasn1-6 | before 4.20.0-2+deb13u1 | 4.20.0-2+deb13u1 |
| Debian:14 | libtasn1-6 | before 4.21.0-2 | 4.21.0-2 |
| openSUSE:Leap 16.0 | libtasn1 | before 4.21.0-160000.1.1 | 4.21.0-160000.1.1 |
| openSUSE:Tumbleweed | libtasn1 | before 4.21.0-1.1 | 4.21.0-1.1 |
| Red Hat:enterprise_linux:10.2 | libtasn1 | before 0:4.20.0-5.el10_2 | 0:4.20.0-5.el10_2 |
| Red Hat:enterprise_linux:10.2 | libtasn1-debuginfo | before 0:4.20.0-5.el10_2 | 0:4.20.0-5.el10_2 |
| Red Hat:enterprise_linux:10.2 | libtasn1-debugsource | before 0:4.20.0-5.el10_2 | 0:4.20.0-5.el10_2 |
| Red Hat:enterprise_linux:10.2 | libtasn1-devel | before 0:4.20.0-5.el10_2 | 0:4.20.0-5.el10_2 |
| Red Hat:enterprise_linux:10.2 | libtasn1-tools | before 0:4.20.0-5.el10_2 | 0:4.20.0-5.el10_2 |
| Red Hat:enterprise_linux:10.2 | libtasn1-tools-debuginfo | before 0:4.20.0-5.el10_2 | 0:4.20.0-5.el10_2 |
| Red Hat:enterprise_linux:8::appstream | libtasn1-debuginfo | before 0:4.13-6.el8_10 | 0:4.13-6.el8_10 |
| Red Hat:enterprise_linux:8::appstream | libtasn1-debugsource | before 0:4.13-6.el8_10 | 0:4.13-6.el8_10 |
| Red Hat:enterprise_linux:8::appstream | libtasn1-devel | before 0:4.13-6.el8_10 | 0:4.13-6.el8_10 |
+21
Same product
gnu: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-46848GNU Libtasn1 before 4.19.0 has an ETYPE_OK off-by-one array size check that affects asn1_encode_simple_der.37Monitor
- CVE-2017-6891Two errors in the "asn1_find_node()" function (lib/parser_aux.c) within GnuTLS libtasn1 version 4.10 can be exploited to cause a stacked-bas37Monitor
- CVE-2016-4008The _asn1_extract_der_octet function in lib/decoding.c in GNU Libtasn1 before 4.8, when used without the ASN1_DECODE_FLAG_STRICT_DER flag, a32Monitor
- CVE-2018-6003An issue was discovered in the _asn1_decode_simple_ber function in decoding.c in GNU Libtasn1 before 4.13.31Monitor
- CVE-2017-10790The _asn1_check_identifier function in GNU Libtasn1 through 4.12 causes a NULL pointer dereference and crash when reading crafted input that31Monitor
- CVE-2015-3622The _asn1_extract_der_octet function in lib/decoding.c in GNU Libtasn1 before 4.5 allows remote attackers to cause a denial of service (out-27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 gnutls 3.8.3-8 on Azure Linux 3.0 | 3.8.3-8 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 libtasn1 4.19.0-2 on Azure Linux 3.0 | 4.19.0-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 libtasn1 4.19.0-3 on Azure Linux 3.0 | 4.19.0-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 gnutls 3.7.11-6 on CBL Mariner 2.0 | 3.7.11-6 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 libtasn1 4.19.0-2 on CBL Mariner 2.0 | 4.19.0-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 libtasn1 4.19.0-3 on CBL Mariner 2.0 | 4.19.0-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:libtasn1 | 4.20.0-5.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:libtasn1-devel | 4.20.0-5.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:libtasn1-tools | 4.20.0-5.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| alpine:libtasn1 | 4.21.0-r0 · Alpine:v3.20 | Package registry (OSV) |
| debian:libtasn1-6 | 4.20.0-2+deb13u1 · Debian:13 | Package registry (OSV) |
| opensuse:libtasn1 | 4.13-150000.4.14.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:libtasn1 | 0:4.20.0-5.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:libtasn1-debuginfo | 0:4.20.0-5.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:libtasn1-debugsource | 0:4.20.0-5.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:libtasn1-devel | 0:4.20.0-5.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:libtasn1-tools | 0:4.20.0-5.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:libtasn1-tools-debuginfo | 0:4.20.0-5.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| rocky linux:libtasn1 | 0:4.20.0-5.el10_2 · Rocky Linux:10 | Package registry (OSV) |
| suse:libtasn1 | 4.13-150000.4.14.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:libtasn1 | 4.9-3.19.1 · SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- This issue was reported Benny ZelsterMicrosoft Security Researchfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.