CVE-2022-49722

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 2025-10-24. 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-2022-54513 (ENISA EUVD) · GHSA-h43m-2hvj-4frc (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: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ice: Fix memory corruption in VF driver

Disable VF's RX/TX queues, when it's disabled. VF can have queues enabled, when it requests a reset. If PF driver assumes that VF is disabled, while VF still has queues configured, VF may unmap DMA resources. In such scenario device still can map packets to memory, which ends up silently corrupting it. Previously, VF driver could experience memory corruption, which lead to crash: [ 5119.170157] BUG: unable to handle kernel paging request at 00001b9780003237 [ 5119.170166] PGD 0 P4D 0 [ 5119.170173] Oops: 0002 [#1] PREEMPT_RT SMP PTI [ 5119.170181] CPU: 30 PID: 427592 Comm: kworker/u96:2 Kdump: loaded Tainted: G W I --------- - - 4.18.0-372.9.1.rt7.166.el8.x86_64 #1 [ 5119.170189] Hardware name: Dell Inc. PowerEdge R740/014X06, BIOS 2.3.10 08/15/2019 [ 5119.170193] Workqueue: iavf iavf_adminq_task [iavf] [ 5119.170219] RIP: 0010:__page_frag_cache_drain+0x5/0x30 [ 5119.170238] Code: 0f 0f b6 77 51 85 f6 74 07 31 d2 e9 05 df ff ff e9 90 fe ff ff 48 8b 05 49 db 33 01 eb b4 0f 1f 80 00 00 00 00 0f 1f 44 00 00 29 77 34 74 01 c3 48 8b 07 f6 c4 80 74 0f 0f b6 77 51 85 f6 74 [ 5119.170244] RSP: 0018:ffffa43b0bdcfd78 EFLAGS: 00010282 [ 5119.170250] RAX: ffffffff896b3e40 RBX: ffff8fb282524000 RCX: 0000000000000002 [ 5119.170254] RDX: 0000000049000000 RSI: 0000000000000000 RDI: 00001b9780003203 [ 5119.170259] RBP: ffff8fb248217b00 R08: 0000000000000022 R09: 0000000000000009 [ 5119.170262] R10: 2b849d6300000000 R11: 0000000000000020 R12: 0000000000000000 [ 5119.170265] R13: 0000000000001000 R14: 0000000000000009 R15: 0000000000000000 [ 5119.170269] FS: 0000000000000000(0000) GS:ffff8fb1201c0000(0000) knlGS:0000000000000000 [ 5119.170274] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 5119.170279] CR2: 00001b9780003237 CR3: 00000008f3e1a003 CR4: 00000000007726e0 [ 5119.170283] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 5119.170286] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 5119.170290] PKRU: 55555554 [ 5119.170292] Call Trace: [ 5119.170298] iavf_clean_rx_ring+0xad/0x110 [iavf] [ 5119.170324] iavf_free_rx_resources+0xe/0x50 [iavf] [ 5119.170342] iavf_free_all_rx_resources.part.51+0x30/0x40 [iavf] [ 5119.170358] iavf_virtchnl_completion+0xd8a/0x15b0 [iavf] [ 5119.170377] ? iavf_clean_arq_element+0x210/0x280 [iavf] [ 5119.170397] iavf_adminq_task+0x126/0x2e0 [iavf] [ 5119.170416] process_one_work+0x18f/0x420 [ 5119.170429] worker_thread+0x30/0x370 [ 5119.170437] ? process_one_work+0x420/0x420 [ 5119.170445] kthread+0x151/0x170 [ 5119.170452] ? set_kthread_struct+0x40/0x40 [ 5119.170460] ret_from_fork+0x35/0x40 [ 5119.170477] Modules linked in: iavf sctp ip6_udp_tunnel udp_tunnel mlx4_en mlx4_core nfp tls vhost_net vhost vhost_iotlb tap tun xt_CHECKSUM ipt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 nft_compat nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache sunrpc intel_rapl_msr iTCO_wdt iTCO_vendor_support dell_smbios wmi_bmof dell_wmi_descriptor dcdbas kvm_intel kvm irqbypass intel_rapl_common isst_if_common skx_edac irdma nfit libnvdimm x86_pkg_temp_thermal i40e intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ib_uverbs rapl ipmi_ssif intel_cstate intel_uncore mei_me pcspkr acpi_ipmi ib_core mei lpc_ich i2c_i801 ipmi_si ipmi_devintf wmi ipmi_msghandler acpi_power_meter xfs libcrc32c sd_mod t10_pi sg mgag200 drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ice ahci drm libahci crc32c_intel libata tg3 megaraid_sas [ 5119.170613] i2c_algo_bit dm_mirror dm_region_hash dm_log dm_mod fuse [last unloaded: iavf] [ 5119.170627] CR2: 00001b9780003237

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.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
0.3%
EPSS %ILE
19th
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
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

February 26, 2025

Last Modified

August 5, 2026

Advisory Details (2)

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

ice: Fix memory corruption in VF driver - kernel/git/stable/linux.git - Linux kernel stable tree

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

ice: Fix memory corruption in VF driver - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1bb8253b1dd44cf004e12c333acc6f25ee286cf3

Vendor Advisories for CVE-2022-49722(3)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-70.26.1.el9_02022-09-20redhat
redhatkernel-0:4.18.0-372.26.1.el8_62022-09-13redhat
linuxKernel @ 5.18.6 (fixes >=5.5.0)—osv

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 ... 7.2~rc5-1~exp1 (498 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.14-1: fixed in 5.18.14-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.14-1: fixed in 5.18.14-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.14-1: fixed in 5.18.14-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 99 of 206 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 107 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-49722?
CVE-2022-49722 is a high-severity vulnerability; its CVE record was published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: ice: Fix memory corruption in VF driver Disable VF's RX/TX queues, when it's disabled. VF can have queues enabled, when it requests a reset. If PF driver assumes that VF is disabled, while VF still has queues configured, VF may…
When was the CVE record for CVE-2022-49722 published?
The CVE record for CVE-2022-49722 was published on February 26, 2025. 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-2022-49722 actively exploited?
CVE-2022-49722 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49722?
CVE-2022-49722 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49722?
A fix for CVE-2022-49722 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49722 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-2022-49722

Explore →

Is Your Infrastructure Affected by CVE-2022-49722?

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

Book a Demo →Browse All CVEs