CVE-2021-46848

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2022-10-24. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2021-33503 (ENISA EUVD) · GHSA-6468-68pw-9chw (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.8%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GNU Libtasn1 before 4.19.0 has an ETYPE_OK off-by-one array size check that affects asn1_encode_simple_der.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation2.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
2.8%
EPSS %ILE
86th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
2.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 24, 2022

Last Modified

October 14, 2026

Advisory Details (9)

Auto-updated Aug 2, 2026
Patch available.
Web page

866237 – (CVE-2021-46848) <dev-libs/libtasn1-4.19.0: Out of bounds read

https://bugs.gentoo.org/866237
Web page

[SECURITY] Fedora 37 Update: mingw-libtasn1-4.19.0-1.fc37 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V5LWOGF7QRMNFRUCZY6TDYQJVFI6MOQ2/
Web page

[SECURITY] Fedora 35 Update: mingw-libtasn1-4.19.0-1.fc35 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OGO7XST4EIJGX4B2ITZCYSWM24534BSU/
Web page

[SECURITY] Fedora 36 Update: libtasn1-4.19.0-1.fc36 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ECM2ELTVRYV4BZ5L5GMIRQE27RFHPAQ6/
Web page

[SECURITY] Fedora 36 Update: mingw-libtasn1-4.19.0-1.fc36 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/AV4SHDJF2XLB4CUPTBPQQ6CLGZ5LKXPZ/
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3263-1] libtasn1-6 security update

https://lists.debian.org/debian-lts-announce/2023/01/msg00003.html
Web page

Out-of-bound access in ETYPE_OK (#32) · Issues · gnutls / libtasn1 · GitLab

https://gitlab.com/gnutls/libtasn1/-/issues/32
Web page

Fix ETYPE_OK off by one array size check. Closes: #32. (44a700d2) · Commits · gnutls / libtasn1 · GitLab

https://gitlab.com/gnutls/libtasn1/-/commit/44a700d2051a666235748970c2df047ff207aeb5

Vendor Advisories for CVE-2021-46848(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibtasn1-doc (4.16.0-2ubuntu0.1+esm1) @ focal2026-11-11ubuntu
ubuntulibtasn1-doc (4.20.0-2ubuntu0.25.10.1) @ questing2026-11-11ubuntu
ubuntulibtasn1-6 (4.7-3ubuntu0.16.04.3+esm3) @ xenial2026-11-11ubuntu
redhatlibtasn1-0:4.13-3.el8_6.12024-01-25redhat
redhatlibtasn1-0:4.16.0-8.el9_12023-01-23redhat
redhatlibtasn1-0:4.13-4.el8_72023-01-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(16 across 16 ecosystems)
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1—
  • every version up to 4.17.0-r1: fixed in 4.17.0-r1
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1—
  • every version up to 4.18.0-r1: fixed in 4.18.0-r1
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1—
  • every version up to 4.18.0-r1: fixed in 4.18.0-r1
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1—
  • every version up to 4.19-r0: fixed in 4.19-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1—
  • every version up to 4.19-r0: fixed in 4.19-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1—
  • every version up to 4.19-r0: fixed in 4.19-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1—
  • every version up to 4.19-r0: fixed in 4.19-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1—
  • every version up to 4.19-r0: fixed in 4.19-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1—
  • every version up to 4.19-r0: fixed in 4.19-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1—
  • every version up to 4.19-r0: fixed in 4.19-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1—
  • every version up to 4.19-r0: fixed in 4.19-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1-64.13-3
  • every version up to 4.13-3+deb10u1: fixed in 4.13-3+deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1-64.16.0-2
  • every version up to 4.16.0-2+deb11u1: fixed in 4.16.0-2+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1-6—
  • every version up to 4.19.0-2: fixed in 4.19.0-2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1-6—
  • every version up to 4.19.0-2: fixed in 4.19.0-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libtasn1-6—
  • every version up to 4.19.0-2: fixed in 4.19.0-2
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 21× in last 7d / 90× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 309 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 209 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:29 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  2. 2026-11-12 11:07 UTCEchelonGraph re-scored
  3. 2026-11-12 11:07 UTCVendor advisory
  4. 2026-11-12 11:07 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  5. 2026-11-11 16:31 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  6. 2026-11-11 10:49 UTCEchelonGraph re-scored
  7. 2026-11-11 10:49 UTCVendor advisory
  8. 2026-11-11 10:49 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  9. 2026-11-10 16:35 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  10. 2026-11-10 10:31 UTCEchelonGraph re-scored
  11. 2026-11-10 10:31 UTCVendor advisory
  12. 2026-11-10 10:31 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-11-09 16:29 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  14. 2026-11-09 10:14 UTCEchelonGraph re-scored
  15. 2026-11-09 10:14 UTCVendor advisory
  16. 2026-11-09 10:14 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  17. 2026-11-08 16:33 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  18. 2026-11-08 09:54 UTCEchelonGraph re-scored
  19. 2026-11-08 09:54 UTCVendor advisory
  20. 2026-11-08 09:54 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-11-07 16:34 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  22. 2026-11-07 09:37 UTCEchelonGraph re-scored
  23. 2026-11-07 09:37 UTCVendor advisory
  24. 2026-11-07 09:37 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  25. 2026-11-06 16:30 UTCEPSS rescoreEPSS 2.8% · 86th percentile
Show 75 more
  1. 2026-11-06 09:20 UTCEchelonGraph re-scored
  2. 2026-11-06 09:20 UTCVendor advisory
  3. 2026-11-06 09:20 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-11-05 16:31 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  5. 2026-11-05 09:03 UTCEchelonGraph re-scored
  6. 2026-11-05 09:03 UTCVendor advisory
  7. 2026-11-05 09:03 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-11-04 16:30 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  9. 2026-11-04 08:46 UTCEchelonGraph re-scored
  10. 2026-11-04 08:46 UTCVendor advisory
  11. 2026-11-04 08:46 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-11-03 22:25 UTCOSV refresh
  13. 2026-11-03 16:38 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  14. 2026-11-03 08:29 UTCEchelonGraph re-scored
  15. 2026-11-03 08:29 UTCVendor advisory
  16. 2026-11-03 08:28 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  17. 2026-11-02 16:38 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  18. 2026-11-02 08:11 UTCEchelonGraph re-scored
  19. 2026-11-02 08:11 UTCVendor advisory
  20. 2026-11-02 08:11 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-11-01 07:55 UTCEchelonGraph re-scored
  22. 2026-11-01 07:55 UTCVendor advisory
  23. 2026-11-01 07:55 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-10-31 16:29 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  25. 2026-10-31 07:37 UTCEchelonGraph re-scored
  26. 2026-10-31 07:37 UTCVendor advisory
  27. 2026-10-31 07:37 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  28. 2026-10-30 16:30 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  29. 2026-10-30 07:20 UTCEchelonGraph re-scored
  30. 2026-10-30 07:20 UTCVendor advisory
  31. 2026-10-30 07:20 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  32. 2026-10-29 16:29 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  33. 2026-10-29 07:03 UTCEchelonGraph re-scored
  34. 2026-10-29 07:03 UTCVendor advisory
  35. 2026-10-29 07:03 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  36. 2026-10-28 16:28 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  37. 2026-10-28 06:46 UTCEchelonGraph re-scored
  38. 2026-10-28 06:46 UTCVendor advisory
  39. 2026-10-28 06:46 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  40. 2026-10-27 16:28 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  41. 2026-10-27 06:29 UTCEchelonGraph re-scored
  42. 2026-10-27 06:29 UTCVendor advisory
  43. 2026-10-27 06:29 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  44. 2026-10-26 16:28 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  45. 2026-10-26 02:18 UTCVendor advisory
  46. 2026-10-26 02:18 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  47. 2026-10-25 18:19 UTCEchelonGraph re-scored
  48. 2026-10-25 16:29 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  49. 2026-10-25 02:01 UTCEchelonGraph re-scored
  50. 2026-10-25 02:01 UTCVendor advisory
  51. 2026-10-25 02:01 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  52. 2026-10-24 16:29 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  53. 2026-10-24 01:45 UTCEchelonGraph re-scored
  54. 2026-10-24 01:45 UTCVendor advisory
  55. 2026-10-24 01:45 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  56. 2026-10-23 16:28 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  57. 2026-10-23 01:27 UTCEchelonGraph re-scored
  58. 2026-10-23 01:27 UTCVendor advisory
  59. 2026-10-23 01:27 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  60. 2026-10-22 16:29 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  61. 2026-10-22 01:10 UTCEchelonGraph re-scored
  62. 2026-10-22 01:10 UTCVendor advisory
  63. 2026-10-22 01:10 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  64. 2026-10-21 16:28 UTCEPSS rescoreEPSS 2.8% · 86th percentile
  65. 2026-10-21 00:52 UTCEchelonGraph re-scored
  66. 2026-10-21 00:52 UTCVendor advisory
  67. 2026-10-21 00:52 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  68. 2026-10-20 16:28 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  69. 2026-10-20 00:34 UTCEchelonGraph re-scored
  70. 2026-10-20 00:34 UTCVendor advisory
  71. 2026-10-20 00:33 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1
  72. 2026-10-19 16:28 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  73. 2026-10-18 23:29 UTCEchelonGraph re-scored
  74. 2026-10-18 23:29 UTCVendor advisory
  75. 2026-10-18 23:29 UTCGHSA enrichmentGHSA-6468-68pw-9chw · GitHub severity CRITICAL · GitHub CVSS 9.1

Frequently asked(5)

What is CVE-2021-46848?
CVE-2021-46848 is a critical-severity vulnerability; its CVE record was published on October 24, 2022. GNU Libtasn1 before 4.19.0 has an ETYPE_OK off-by-one array size check that affects asn1_encode_simple_der.
When was the CVE record for CVE-2021-46848 published?
The CVE record for CVE-2021-46848 was published on October 24, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2021-46848 actively exploited?
CVE-2021-46848 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.8% probability of exploitation in the next 30 days (86th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-46848?
CVE-2021-46848 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2021-46848?
A fix for CVE-2021-46848 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-46848 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-46848

Explore →

Is Your Infrastructure Affected by CVE-2021-46848?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.