CVE-2022-50163

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-55428 (ENISA EUVD) · GHSA-qv7x-xghp-vpfc (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:

ax25: fix incorrect dev_tracker usage

While investigating a separate rose issue [1], and enabling CONFIG_NET_DEV_REFCNT_TRACKER=y, Bernard reported an orthogonal ax25 issue [2]

An ax25_dev can be used by one (or many) struct ax25_cb. We thus need different dev_tracker, one per struct ax25_cb.

After this patch is applied, we are able to focus on rose.

[1] https://lore.kernel.org/netdev/[email protected]/

[2] [ 205.798723] reference already released. [ 205.798732] allocated in: [ 205.798734] ax25_bind+0x1a2/0x230 [ax25] [ 205.798747] __sys_bind+0xea/0x110 [ 205.798753] __x64_sys_bind+0x18/0x20 [ 205.798758] do_syscall_64+0x5c/0x80 [ 205.798763] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 205.798768] freed in: [ 205.798770] ax25_release+0x115/0x370 [ax25] [ 205.798778] __sock_release+0x42/0xb0 [ 205.798782] sock_close+0x15/0x20 [ 205.798785] __fput+0x9f/0x260 [ 205.798789] ____fput+0xe/0x10 [ 205.798792] task_work_run+0x64/0xa0 [ 205.798798] exit_to_user_mode_prepare+0x18b/0x190 [ 205.798804] syscall_exit_to_user_mode+0x26/0x40 [ 205.798808] do_syscall_64+0x69/0x80 [ 205.798812] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 205.798827] ------------[ cut here ]------------ [ 205.798829] WARNING: CPU: 2 PID: 2605 at lib/ref_tracker.c:136 ref_tracker_free.cold+0x60/0x81 [ 205.798837] Modules linked in: rose netrom mkiss ax25 rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi nls_iso8859_1 i915 rtw88_8821ce rtw88_8821c x86_pkg_temp_thermal rtw88_pci intel_powerclamp rtw88_core snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio coretemp snd_hda_intel kvm_intel snd_intel_dspcfg mac80211 snd_hda_codec kvm i2c_algo_bit drm_buddy drm_dp_helper btusb drm_kms_helper snd_hwdep btrtl snd_hda_core btbcm joydev crct10dif_pclmul btintel crc32_pclmul ghash_clmulni_intel mei_hdcp btmtk intel_rapl_msr aesni_intel bluetooth input_leds snd_pcm crypto_simd syscopyarea processor_thermal_device_pci_legacy sysfillrect cryptd intel_soc_dts_iosf snd_seq sysimgblt ecdh_generic fb_sys_fops rapl libarc4 processor_thermal_device intel_cstate processor_thermal_rfim cec snd_timer ecc snd_seq_device cfg80211 processor_thermal_mbox mei_me processor_thermal_rapl mei rc_core at24 snd intel_pch_thermal intel_rapl_common ttm soundcore int340x_thermal_zone video [ 205.798948] mac_hid acpi_pad sch_fq_codel ipmi_devintf ipmi_msghandler drm msr parport_pc ppdev lp parport ramoops pstore_blk reed_solomon pstore_zone efi_pstore ip_tables x_tables autofs4 hid_generic usbhid hid i2c_i801 i2c_smbus r8169 xhci_pci ahci libahci realtek lpc_ich xhci_pci_renesas [last unloaded: ax25] [ 205.798992] CPU: 2 PID: 2605 Comm: ax25ipd Not tainted 5.18.11-F6BVP #3 [ 205.798996] Hardware name: To be filled by O.E.M. To be filled by O.E.M./CK3, BIOS 5.011 09/16/2020 [ 205.798999] RIP: 0010:ref_tracker_free.cold+0x60/0x81 [ 205.799005] Code: e8 d2 01 9b ff 83 7b 18 00 74 14 48 c7 c7 2f d7 ff 98 e8 10 6e fc ff 8b 7b 18 e8 b8 01 9b ff 4c 89 ee 4c 89 e7 e8 5d fd 07 00 <0f> 0b b8 ea ff ff ff e9 30 05 9b ff 41 0f b6 f7 48 c7 c7 a0 fa 4e [ 205.799008] RSP: 0018:ffffaf5281073958 EFLAGS: 00010286 [ 205.799011] RAX: 0000000080000000 RBX: ffff9a0bd687ebe0 RCX: 0000000000000000 [ 205.799014] RDX: 0000000000000001 RSI: 0000000000000282 RDI: 00000000ffffffff [ 205.799016] RBP: ffffaf5281073a10 R08: 0000000000000003 R09: fffffffffffd5618 [ 205.799019] R10: 0000000000ffff10 R11: 000000000000000f R12: ffff9a0bc53384d0 [ 205.799022] R13: 0000000000000282 R14: 00000000ae000001 R15: 0000000000000001 [ 205.799024] FS: 0000000000000000(0000) GS:ffff9a0d0f300000(0000) knlGS:0000000000000000 [ 205.799028] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 205.799031] CR2: 00007ff6b8311554 CR3: 000000001ac10004 CR4: 00000000001706e0 [ 205.799033] Call Trace: [ 205.799035] [ 205.799038] ? ax25_dev_device_down+0xd9/ ---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.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
17th
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-11-03). 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 18, 2025

Advisory Details (3)

Auto-updated Sep 30, 2026
Patch available.
Web page

ax25: fix incorrect dev_tracker usage - kernel/git/stable/linux.git - Linux kernel stable tree

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

ax25: fix incorrect dev_tracker usage - kernel/git/stable/linux.git - Linux kernel stable tree

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

ax25: fix incorrect dev_tracker usage - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4294df1374450912b2f64ee3cf575069fc784679

Vendor Advisories for CVE-2022-50163(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.18.18 (fixes >=5.17.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 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.19.6-1: fixed in 5.19.6-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.19.6-1: fixed in 5.19.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.19.6-1: fixed in 5.19.6-1
—

Data Freshness Timeline

(refreshed 10× in last 7d / 44× 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 201 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 102 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2022-50163?
CVE-2022-50163 is a high-severity vulnerability; its CVE record was published on June 18, 2025. In the Linux kernel, the following vulnerability has been resolved: ax25: fix incorrect dev_tracker usage While investigating a separate rose issue [1], and enabling CONFIG_NET_DEV_REFCNT_TRACKER=y, Bernard reported an orthogonal ax25 issue [2] An ax25_dev can be used by one (or many) struct…
When was the CVE record for CVE-2022-50163 published?
The CVE record for CVE-2022-50163 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 18, 2025; the record at its source may have been updated since.
Is CVE-2022-50163 actively exploited?
CVE-2022-50163 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50163?
CVE-2022-50163 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-50163?
A fix for CVE-2022-50163 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-50163 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-50163

Explore →

Is Your Infrastructure Affected by CVE-2022-50163?

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

Book a Demo →Browse All CVEs