CVE-2021-47103

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-03-04. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2021-33751 (ENISA EUVD) · GHSA-rpv2-375w-83vr (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

inet: fully convert sk->sk_rx_dst to RCU rules

syzbot reported various issues around early demux, one being included in this changelog [1]

sk->sk_rx_dst is using RCU protection without clearly documenting it.

And following sequences in tcp_v4_do_rcv()/tcp_v6_do_rcv() are not following standard RCU rules.

[a] dst_release(dst); [b] sk->sk_rx_dst = NULL;

They look wrong because a delete operation of RCU protected pointer is supposed to clear the pointer before the call_rcu()/synchronize_rcu() guarding actual memory freeing.

In some cases indeed, dst could be freed before [b] is done.

We could cheat by clearing sk_rx_dst before calling dst_release(), but this seems the right time to stick to standard RCU annotations and debugging facilities.

[1] BUG: KASAN: use-after-free in dst_check include/net/dst.h:470 [inline] BUG: KASAN: use-after-free in tcp_v4_early_demux+0x95b/0x960 net/ipv4/tcp_ipv4.c:1792 Read of size 2 at addr ffff88807f1cb73a by task syz-executor.5/9204

CPU: 0 PID: 9204 Comm: syz-executor.5 Not tainted 5.16.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description.constprop.0.cold+0x8d/0x320 mm/kasan/report.c:247 __kasan_report mm/kasan/report.c:433 [inline] kasan_report.cold+0x83/0xdf mm/kasan/report.c:450 dst_check include/net/dst.h:470 [inline] tcp_v4_early_demux+0x95b/0x960 net/ipv4/tcp_ipv4.c:1792 ip_rcv_finish_core.constprop.0+0x15de/0x1e80 net/ipv4/ip_input.c:340 ip_list_rcv_finish.constprop.0+0x1b2/0x6e0 net/ipv4/ip_input.c:583 ip_sublist_rcv net/ipv4/ip_input.c:609 [inline] ip_list_rcv+0x34e/0x490 net/ipv4/ip_input.c:644 __netif_receive_skb_list_ptype net/core/dev.c:5508 [inline] __netif_receive_skb_list_core+0x549/0x8e0 net/core/dev.c:5556 __netif_receive_skb_list net/core/dev.c:5608 [inline] netif_receive_skb_list_internal+0x75e/0xd80 net/core/dev.c:5699 gro_normal_list net/core/dev.c:5853 [inline] gro_normal_list net/core/dev.c:5849 [inline] napi_complete_done+0x1f1/0x880 net/core/dev.c:6590 virtqueue_napi_complete drivers/net/virtio_net.c:339 [inline] virtnet_poll+0xca2/0x11b0 drivers/net/virtio_net.c:1557 __napi_poll+0xaf/0x440 net/core/dev.c:7023 napi_poll net/core/dev.c:7090 [inline] net_rx_action+0x801/0xb40 net/core/dev.c:7177 __do_softirq+0x29b/0x9c2 kernel/softirq.c:558 invoke_softirq kernel/softirq.c:432 [inline] __irq_exit_rcu+0x123/0x180 kernel/softirq.c:637 irq_exit_rcu+0x5/0x20 kernel/softirq.c:649 common_interrupt+0x52/0xc0 arch/x86/kernel/irq.c:240 asm_common_interrupt+0x1e/0x40 arch/x86/include/asm/idtentry.h:629 RIP: 0033:0x7f5e972bfd57 Code: 39 d1 73 14 0f 1f 80 00 00 00 00 48 8b 50 f8 48 83 e8 08 48 39 ca 77 f3 48 39 c3 73 3e 48 89 13 48 8b 50 f8 48 89 38 49 8b 0e <48> 8b 3e 48 83 c3 08 48 83 c6 08 eb bc 48 39 d1 72 9e 48 39 d0 73 RSP: 002b:00007fff8a413210 EFLAGS: 00000283 RAX: 00007f5e97108990 RBX: 00007f5e97108338 RCX: ffffffff81d3aa45 RDX: ffffffff81d3aa45 RSI: 00007f5e97108340 RDI: ffffffff81d3aa45 RBP: 00007f5e97107eb8 R08: 00007f5e97108d88 R09: 0000000093c2e8d9 R10: 0000000000000000 R11: 0000000000000000 R12: 00007f5e97107eb0 R13: 00007f5e97108338 R14: 00007f5e97107ea8 R15: 0000000000000019

Allocated by task 13: kasan_save_stack+0x1e/0x50 mm/kasan/common.c:38 kasan_set_track mm/kasan/common.c:46 [inline] set_alloc_info mm/kasan/common.c:434 [inline] __kasan_slab_alloc+0x90/0xc0 mm/kasan/common.c:467 kasan_slab_alloc include/linux/kasan.h:259 [inline] slab_post_alloc_hook mm/slab.h:519 [inline] slab_alloc_node mm/slub.c:3234 [inline] slab_alloc mm/slub.c:3242 [inline] kmem_cache_alloc+0x202/0x3a0 mm/slub.c:3247 dst_alloc+0x146/0x1f0 net/core/dst.c:92 rt_dst_alloc+0x73/0x430 net/ipv4/route.c:1613 ip_route_input_slow+0x1817/0x3a20 net/ipv4/route.c:234 ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
1.0%
EPSS %ILE
61st
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

March 4, 2024

Last Modified

August 5, 2026

Advisory Details (7)

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

inet: fully convert sk->sk_rx_dst to RCU rules - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/75a578000ae5e511e5d0e8433c94a14d9c99c412
Web page

inet: fully convert sk->sk_rx_dst to RCU rules - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/68c34ce11ef23328692aa35fa6aaafdd75913100
Web page

inet: fully convert sk->sk_rx_dst to RCU rules - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0249a4b8a554f2eb6a27b62516fa50168584faa4
Web page

inet: fully convert sk->sk_rx_dst to RCU rules - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f039b43cbaea5e0700980c2f0052da05a70782e0
Web page

inet: fully convert sk->sk_rx_dst to RCU rules - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c3bb4a7e8cbc984e1cdac0fe6af60e880214ed6e
Web page

inet: fully convert sk->sk_rx_dst to RCU rules - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92e6e36ecd16808866ac6172b9491b5097cde449
Web page

inet: fully convert sk->sk_rx_dst to RCU rules - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8f905c0e7354ef261360fb7535ea079b1082c105

Vendor Advisories for CVE-2021-47103(2)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-kvm (4.4.0.1142.139) @ xenial2026-10-28ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.266.300~14.04.1) @ trusty2026-10-28ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.266.272) @ xenial2026-10-28ubuntu
redhatkernel-0:5.14.0-162.6.1.el9_12022-11-15redhat
redhatkernel-0:4.18.0-425.3.1.el82022-11-08redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (22 versions)
  • every version up to 5.10.158-1: fixed in 5.10.158-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.15.15-1: fixed in 5.15.15-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.15.15-1: fixed in 5.15.15-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.15.15-1: fixed in 5.15.15-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 39× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 97 of 219 refreshes 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 122 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-31 16:29 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  2. 2026-10-30 16:30 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  3. 2026-10-29 16:29 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  4. 2026-10-28 16:28 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  5. 2026-10-28 15:50 UTCEG score recompute
  6. 2026-10-28 15:50 UTCVendor advisory
  7. 2026-10-28 15:50 UTCGHSA enrichmentGHSA-rpv2-375w-83vr · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-10-27 16:28 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  9. 2026-10-26 16:28 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  10. 2026-10-25 18:18 UTCEG score recompute
  11. 2026-10-25 16:29 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  12. 2026-10-24 16:29 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  13. 2026-10-23 16:28 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  14. 2026-10-22 16:29 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  15. 2026-10-21 16:28 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  16. 2026-10-21 08:34 UTCEG score recompute
  17. 2026-10-21 08:34 UTCVendor advisory
  18. 2026-10-21 08:34 UTCGHSA enrichmentGHSA-rpv2-375w-83vr · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-10-20 16:28 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  20. 2026-10-19 16:28 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  21. 2026-10-19 13:25 UTCOSV refresh
  22. 2026-10-18 16:28 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  23. 2026-10-18 08:49 UTCEG score recompute
  24. 2026-10-17 16:29 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  25. 2026-10-16 16:34 UTCEPSS rescoreEPSS 1.0% · 60th percentile
Show 72 more
  1. 2026-10-15 16:28 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  2. 2026-10-14 16:29 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  3. 2026-10-13 16:28 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  4. 2026-10-12 19:05 UTCEG score recompute
  5. 2026-10-12 16:30 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  6. 2026-10-11 23:31 UTCEG score recompute
  7. 2026-10-11 13:44 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  8. 2026-10-10 19:56 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  9. 2026-10-09 20:04 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  10. 2026-10-08 16:40 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  11. 2026-10-07 23:45 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  12. 2026-10-06 15:14 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  13. 2026-10-05 17:40 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  14. 2026-10-04 23:19 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  15. 2026-10-03 14:22 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  16. 2026-10-02 16:23 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  17. 2026-09-30 15:45 UTCEG score recompute
  18. 2026-09-30 15:00 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  19. 2026-09-29 15:15 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  20. 2026-09-28 13:47 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  21. 2026-09-26 20:33 UTCOSV refresh
  22. 2026-09-26 15:54 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  23. 2026-09-26 00:21 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  24. 2026-09-24 14:00 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  25. 2026-09-23 13:45 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  26. 2026-09-22 14:44 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  27. 2026-09-21 20:28 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  28. 2026-09-20 20:13 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  29. 2026-09-19 15:38 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  30. 2026-09-18 19:24 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  31. 2026-09-17 19:23 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  32. 2026-09-16 14:05 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  33. 2026-09-15 03:06 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  34. 2026-09-12 14:57 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  35. 2026-09-11 14:49 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  36. 2026-09-11 09:33 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  37. 2026-09-08 21:57 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  38. 2026-09-07 15:58 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  39. 2026-09-07 05:47 UTCOSV refresh
  40. 2026-09-06 13:45 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  41. 2026-09-05 15:25 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  42. 2026-09-04 13:57 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  43. 2026-09-04 05:03 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  44. 2026-09-02 14:09 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  45. 2026-09-01 13:51 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  46. 2026-08-30 19:14 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  47. 2026-08-30 01:19 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  48. 2026-08-28 21:38 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  49. 2026-08-27 14:22 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  50. 2026-08-26 14:43 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  51. 2026-08-25 13:46 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  52. 2026-08-24 14:13 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  53. 2026-08-21 23:46 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  54. 2026-08-20 22:52 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  55. 2026-08-20 15:31 UTCOSV refresh
  56. 2026-08-19 17:01 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  57. 2026-08-18 13:45 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  58. 2026-08-17 13:44 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  59. 2026-08-16 14:53 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  60. 2026-08-16 02:11 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  61. 2026-08-15 01:27 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  62. 2026-08-13 21:57 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  63. 2026-08-12 13:48 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  64. 2026-08-11 13:38 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  65. 2026-08-09 13:44 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  66. 2026-08-08 16:34 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  67. 2026-08-07 16:24 UTCEPSS rescoreEPSS 1.0% · 58th percentile
  68. 2026-08-06 13:44 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  69. 2026-08-05 19:15 UTCEPSS rescoreEPSS 1.0% · 57th percentile
  70. 2026-08-05 09:43 UTCEG score recompute
  71. 2026-08-05 09:43 UTCVendor advisory
  72. 2026-08-05 09:43 UTCGHSA enrichmentGHSA-rpv2-375w-83vr · GitHub severity HIGH · GitHub CVSS 7.8

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2021-47103?
CVE-2021-47103 is a high-severity vulnerability; its CVE record was published on March 4, 2024. In the Linux kernel, the following vulnerability has been resolved: inet: fully convert sk->sk_rx_dst to RCU rules syzbot reported various issues around early demux, one being included in this changelog [1] sk->sk_rx_dst is using RCU protection without clearly documenting it. And following…
When was the CVE record for CVE-2021-47103 published?
The CVE record for CVE-2021-47103 was published on March 4, 2024. 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2021-47103 actively exploited?
CVE-2021-47103 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-47103?
CVE-2021-47103 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2021-47103?
A fix for CVE-2021-47103 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-47103 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-47103

Explore →

Is Your Infrastructure Affected by CVE-2021-47103?

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

Book a Demo →Browse All CVEs