CVE-2022-50214

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-06-18. 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-55476 (ENISA EUVD) · GHSA-c35q-x63g-2qfh (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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

coresight: Clear the connection field properly

coresight devices track their connections (output connections) and hold a reference to the fwnode. When a device goes away, we walk through the devices on the coresight bus and make sure that the references are dropped. This happens both ways: a) For all output connections from the device, drop the reference to the target device via coresight_release_platform_data()

b) Iterate over all the devices on the coresight bus and drop the reference to fwnode if *this* device is the target of the output connection, via coresight_remove_conns()->coresight_remove_match().

However, the coresight_remove_match() doesn't clear the fwnode field, after dropping the reference, this causes use-after-free and additional refcount drops on the fwnode.

e.g., if we have two devices, A and B, with a connection, A -> B. If we remove B first, B would clear the reference on B, from A via coresight_remove_match(). But when A is removed, it still has a connection with fwnode still pointing to B. Thus it tries to drops the reference in coresight_release_platform_data(), raising the bells like :

[ 91.990153] ------------[ cut here ]------------ [ 91.990163] refcount_t: addition on 0; use-after-free. [ 91.990212] WARNING: CPU: 0 PID: 461 at lib/refcount.c:25 refcount_warn_saturate+0xa0/0x144 [ 91.990260] Modules linked in: coresight_funnel coresight_replicator coresight_etm4x(-) crct10dif_ce coresight ip_tables x_tables ipv6 [last unloaded: coresight_cpu_debug] [ 91.990398] CPU: 0 PID: 461 Comm: rmmod Tainted: G W T 5.19.0-rc2+ #53 [ 91.990418] Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform, BIOS EDK II Feb 1 2019 [ 91.990434] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 91.990454] pc : refcount_warn_saturate+0xa0/0x144 [ 91.990476] lr : refcount_warn_saturate+0xa0/0x144 [ 91.990496] sp : ffff80000c843640 [ 91.990509] x29: ffff80000c843640 x28: ffff800009957c28 x27: ffff80000c8439a8 [ 91.990560] x26: ffff00097eff1990 x25: ffff8000092b6ad8 x24: ffff00097eff19a8 [ 91.990610] x23: ffff80000c8439a8 x22: 0000000000000000 x21: ffff80000c8439c2 [ 91.990659] x20: 0000000000000000 x19: ffff00097eff1a10 x18: ffff80000ab99c40 [ 91.990708] x17: 0000000000000000 x16: 0000000000000000 x15: ffff80000abf6fa0 [ 91.990756] x14: 000000000000001d x13: 0a2e656572662d72 x12: 657466612d657375 [ 91.990805] x11: 203b30206e6f206e x10: 6f69746964646120 x9 : ffff8000081aba28 [ 91.990854] x8 : 206e6f206e6f6974 x7 : 69646461203a745f x6 : 746e756f63666572 [ 91.990903] x5 : ffff00097648ec58 x4 : 0000000000000000 x3 : 0000000000000027 [ 91.990952] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff00080260ba00 [ 91.991000] Call trace: [ 91.991012] refcount_warn_saturate+0xa0/0x144 [ 91.991034] kobject_get+0xac/0xb0 [ 91.991055] of_node_get+0x2c/0x40 [ 91.991076] of_fwnode_get+0x40/0x60 [ 91.991094] fwnode_handle_get+0x3c/0x60 [ 91.991116] fwnode_get_nth_parent+0xf4/0x110 [ 91.991137] fwnode_full_name_string+0x48/0xc0 [ 91.991158] device_node_string+0x41c/0x530 [ 91.991178] pointer+0x320/0x3ec [ 91.991198] vsnprintf+0x23c/0x750 [ 91.991217] vprintk_store+0x104/0x4b0 [ 91.991238] vprintk_emit+0x8c/0x360 [ 91.991257] vprintk_default+0x44/0x50 [ 91.991276] vprintk+0xcc/0xf0 [ 91.991295] _printk+0x68/0x90 [ 91.991315] of_node_release+0x13c/0x14c [ 91.991334] kobject_put+0x98/0x114 [ 91.991354] of_node_put+0x24/0x34 [ 91.991372] of_fwnode_put+0x40/0x5c [ 91.991390] fwnode_handle_put+0x38/0x50 [ 91.991411] coresight_release_platform_data+0x74/0xb0 [coresight] [ 91.991472] coresight_unregister+0x64/0xcc [coresight] [ 91.991525] etm4_remove_dev+0x64/0x78 [coresight_etm4x] [ 91.991563] etm4_remove_amba+0x1c/0x2c [coresight_etm4x] [ 91.991598] amba_remove+0x3c/0x19c ---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.2% × 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.2%
EPSS %ILE
14th
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.2% 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 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

June 18, 2025

Last Modified

November 19, 2025

Advisory Details (6)

Auto-updated Oct 21, 2026
Patch available.
Web page

coresight: Clear the connection field properly - kernel/git/stable/linux.git - Linux kernel stable tree

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

coresight: Clear the connection field properly - kernel/git/stable/linux.git - Linux kernel stable tree

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

coresight: Clear the connection field properly - kernel/git/stable/linux.git - Linux kernel stable tree

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

coresight: Clear the connection field properly - kernel/git/stable/linux.git - Linux kernel stable tree

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

coresight: Clear the connection field properly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/847b9273dd61567fb77617eabc5fa002594db062
Web page

coresight: Clear the connection field properly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2af89ebacf299b7fba5f3087d35e8a286ec33706

Vendor Advisories for CVE-2022-50214(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 5.4.211 (fixes >=5.3.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 ... 5.10.92-2 (18 versions)
  • every version up to 5.10.140-1: fixed in 5.10.140-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.2-1: fixed in 6.0.2-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.2-1: fixed in 6.0.2-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.2-1: fixed in 6.0.2-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-50214?
CVE-2022-50214 is a high-severity vulnerability; its CVE record was published on June 18, 2025. In the Linux kernel, the following vulnerability has been resolved: coresight: Clear the connection field properly coresight devices track their connections (output connections) and hold a reference to the fwnode. When a device goes away, we walk through the devices on the coresight bus and make…
When was the CVE record for CVE-2022-50214 published?
The CVE record for CVE-2022-50214 was published on June 18, 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 November 19, 2025; the record at its source may have been updated since.
Is CVE-2022-50214 actively exploited?
CVE-2022-50214 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50214?
CVE-2022-50214 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-50214?
A fix for CVE-2022-50214 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-50214 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-50214

Explore →

Is Your Infrastructure Affected by CVE-2022-50214?

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

Book a Demo →Browse All CVEs