CVE-2022-49543

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory (severity: MODERATE) published 2025-10-22. NVD baseline CVSS 5.5; sources differ by 0.0.

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

Also known asEUVD-2022-54475 (ENISA EUVD) · GHSA-p6c8-wm8r-hj4h (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ath11k: fix the warning of dev_wake in mhi_pm_disable_transition()

When test device recovery with below command, it has warning in message as below. echo assert > /sys/kernel/debug/ath11k/wcn6855\ hw2.0/simulate_fw_crash echo assert > /sys/kernel/debug/ath11k/qca6390\ hw2.0/simulate_fw_crash

warning message: [ 1965.642121] ath11k_pci 0000:06:00.0: simulating firmware assert crash [ 1968.471364] ieee80211 phy0: Hardware restart was requested [ 1968.511305] ------------[ cut here ]------------ [ 1968.511368] WARNING: CPU: 3 PID: 1546 at drivers/bus/mhi/core/pm.c:505 mhi_pm_disable_transition+0xb37/0xda0 [mhi] [ 1968.511443] Modules linked in: ath11k_pci ath11k mac80211 libarc4 cfg80211 qmi_helpers qrtr_mhi mhi qrtr nvme nvme_core [ 1968.511563] CPU: 3 PID: 1546 Comm: kworker/u17:0 Kdump: loaded Tainted: G W 5.17.0-rc3-wt-ath+ #579 [ 1968.511629] Hardware name: Intel(R) Client Systems NUC8i7HVK/NUC8i7HVB, BIOS HNKBLi70.86A.0067.2021.0528.1339 05/28/2021 [ 1968.511704] Workqueue: mhi_hiprio_wq mhi_pm_st_worker [mhi] [ 1968.511787] RIP: 0010:mhi_pm_disable_transition+0xb37/0xda0 [mhi] [ 1968.511870] Code: a9 fe ff ff 4c 89 ff 44 89 04 24 e8 03 46 f6 e5 44 8b 04 24 41 83 f8 01 0f 84 21 fe ff ff e9 4c fd ff ff 0f 0b e9 af f8 ff ff <0f> 0b e9 5c f8 ff ff 48 89 df e8 da 9e ee e3 e9 12 fd ff ff 4c 89 [ 1968.511923] RSP: 0018:ffffc900024efbf0 EFLAGS: 00010286 [ 1968.511969] RAX: 00000000ffffffff RBX: ffff88811d241250 RCX: ffffffffc0176922 [ 1968.512014] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffff888118a90a24 [ 1968.512059] RBP: ffff888118a90800 R08: 0000000000000000 R09: ffff888118a90a27 [ 1968.512102] R10: ffffed1023152144 R11: 0000000000000001 R12: ffff888118a908ac [ 1968.512229] R13: ffff888118a90928 R14: dffffc0000000000 R15: ffff888118a90a24 [ 1968.512310] FS: 0000000000000000(0000) GS:ffff888234200000(0000) knlGS:0000000000000000 [ 1968.512405] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1968.512493] CR2: 00007f5538f443a8 CR3: 000000016dc28001 CR4: 00000000003706e0 [ 1968.512587] Call Trace: [ 1968.512672] [ 1968.512751] ? _raw_spin_unlock_irq+0x1f/0x40 [ 1968.512859] mhi_pm_st_worker+0x3ac/0x790 [mhi] [ 1968.512959] ? mhi_pm_mission_mode_transition.isra.0+0x7d0/0x7d0 [mhi] [ 1968.513063] process_one_work+0x86a/0x1400 [ 1968.513184] ? pwq_dec_nr_in_flight+0x230/0x230 [ 1968.513312] ? move_linked_works+0x125/0x290 [ 1968.513416] worker_thread+0x6db/0xf60 [ 1968.513536] ? process_one_work+0x1400/0x1400 [ 1968.513627] kthread+0x241/0x2d0 [ 1968.513733] ? kthread_complete_and_exit+0x20/0x20 [ 1968.513821] ret_from_fork+0x22/0x30 [ 1968.513924]

Reason is mhi_deassert_dev_wake() from mhi_device_put() is called but mhi_assert_dev_wake() from __mhi_device_get_sync() is not called in progress of recovery. Commit 8e0559921f9a ("bus: mhi: core: Skip device wake in error or shutdown state") add check for the pm_state of mhi in __mhi_device_get_sync(), and the pm_state is not the normal state untill recovery is completed, so it leads the dev_wake is not 0 and above warning print in mhi_pm_disable_transition() while checking mhi_cntrl->dev_wake.

Add check in ath11k_pci_write32()/ath11k_pci_read32() to skip call mhi_device_put() if mhi_device_get_sync() does not really do wake, then the warning gone.

Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03003-QCAHSPSWPL_V1_V2_SILICONZ_LITE-2

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-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-07). 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 15, 2026

Advisory Details (3)

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

ath11k: fix the warning of dev_wake in mhi_pm_disable_transition() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d7a8a6204ea9271f1d0a8c66a9fd2f54d2e3cbc
Web page

ath11k: fix the warning of dev_wake in mhi_pm_disable_transition() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ath11k: fix the warning of dev_wake in mhi_pm_disable_transition() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f18206cddae033c488e4879f198699092ca0524

Vendor Advisories for CVE-2022-49543(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-162.6.1.el9_12022-11-15redhat
redhatkernel-0:4.18.0-425.3.1.el82022-11-08redhat
linuxKernel @ 5.17.14 (fixes >=5.10.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.18.5-1: fixed in 5.18.5-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-1
—

Data Freshness Timeline

(refreshed 6× in last 7d / 32× 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 216 rows on record for this CVE, as 99 entries (1 repeat merged).

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 116 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2022-49543?
CVE-2022-49543 is a medium-severity vulnerability; its CVE record was published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: ath11k: fix the warning of dev_wake in mhi_pm_disable_transition() When test device recovery with below command, it has warning in message as below. echo assert > /sys/kernel/debug/ath11k/wcn6855\ hw2.0/simulate_fw_crash echo…
When was the CVE record for CVE-2022-49543 published?
The CVE record for CVE-2022-49543 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 15, 2026; the record at its source may have been updated since.
Is CVE-2022-49543 actively exploited?
CVE-2022-49543 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-49543?
CVE-2022-49543 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49543?
A fix for CVE-2022-49543 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49543 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-49543

Explore →

Is Your Infrastructure Affected by CVE-2022-49543?

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

Book a Demo →Browse All CVEs