CVE-2022-49465

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-02-27. 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-54764 (ENISA EUVD) · GHSA-xp9j-268q-p7q6 (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:

blk-throttle: Set BIO_THROTTLED when bio has been throttled

1.In current process, all bio will set the BIO_THROTTLED flag after __blk_throtl_bio().

2.If bio needs to be throttled, it will start the timer and stop submit bio directly. Bio will submit in blk_throtl_dispatch_work_fn() when the timer expires.But in the current process, if bio is throttled. The BIO_THROTTLED will be set to bio after timer start. If the bio has been completed, it may cause use-after-free blow.

BUG: KASAN: use-after-free in blk_throtl_bio+0x12f0/0x2c70 Read of size 2 at addr ffff88801b8902d4 by task fio/26380

dump_stack+0x9b/0xce print_address_description.constprop.6+0x3e/0x60 kasan_report.cold.9+0x22/0x3a blk_throtl_bio+0x12f0/0x2c70 submit_bio_checks+0x701/0x1550 submit_bio_noacct+0x83/0xc80 submit_bio+0xa7/0x330 mpage_readahead+0x380/0x500 read_pages+0x1c1/0xbf0 page_cache_ra_unbounded+0x471/0x6f0 do_page_cache_ra+0xda/0x110 ondemand_readahead+0x442/0xae0 page_cache_async_ra+0x210/0x300 generic_file_buffered_read+0x4d9/0x2130 generic_file_read_iter+0x315/0x490 blkdev_read_iter+0x113/0x1b0 aio_read+0x2ad/0x450 io_submit_one+0xc8e/0x1d60 __se_sys_io_submit+0x125/0x350 do_syscall_64+0x2d/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xa9

Allocated by task 26380: kasan_save_stack+0x19/0x40 __kasan_kmalloc.constprop.2+0xc1/0xd0 kmem_cache_alloc+0x146/0x440 mempool_alloc+0x125/0x2f0 bio_alloc_bioset+0x353/0x590 mpage_alloc+0x3b/0x240 do_mpage_readpage+0xddf/0x1ef0 mpage_readahead+0x264/0x500 read_pages+0x1c1/0xbf0 page_cache_ra_unbounded+0x471/0x6f0 do_page_cache_ra+0xda/0x110 ondemand_readahead+0x442/0xae0 page_cache_async_ra+0x210/0x300 generic_file_buffered_read+0x4d9/0x2130 generic_file_read_iter+0x315/0x490 blkdev_read_iter+0x113/0x1b0 aio_read+0x2ad/0x450 io_submit_one+0xc8e/0x1d60 __se_sys_io_submit+0x125/0x350 do_syscall_64+0x2d/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xa9

Freed by task 0: kasan_save_stack+0x19/0x40 kasan_set_track+0x1c/0x30 kasan_set_free_info+0x1b/0x30 __kasan_slab_free+0x111/0x160 kmem_cache_free+0x94/0x460 mempool_free+0xd6/0x320 bio_free+0xe0/0x130 bio_put+0xab/0xe0 bio_endio+0x3a6/0x5d0 blk_update_request+0x590/0x1370 scsi_end_request+0x7d/0x400 scsi_io_completion+0x1aa/0xe50 scsi_softirq_done+0x11b/0x240 blk_mq_complete_request+0xd4/0x120 scsi_mq_done+0xf0/0x200 virtscsi_vq_done+0xbc/0x150 vring_interrupt+0x179/0x390 __handle_irq_event_percpu+0xf7/0x490 handle_irq_event_percpu+0x7b/0x160 handle_irq_event+0xcc/0x170 handle_edge_irq+0x215/0xb20 common_interrupt+0x60/0x120 asm_common_interrupt+0x1e/0x40

Fix this by move BIO_THROTTLED set into the queue_lock.

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 SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
0.3%
EPSS %ILE
22nd
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-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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)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 Vulnrichment) · Technical impact total (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

February 26, 2025

Last Modified

August 5, 2026

Advisory Details (5)

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

blk-throttle: Set BIO_THROTTLED when bio has been throttled - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5a011f889b4832aa80c2a872a5aade5c48d2756f
Web page

blk-throttle: Set BIO_THROTTLED when bio has been throttled - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/935fa666534d7b7185e8c6b0191cd06281be4290
Web page

blk-throttle: Set BIO_THROTTLED when bio has been throttled - kernel/git/stable/linux.git - Linux kernel stable tree

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

blk-throttle: Set BIO_THROTTLED when bio has been throttled - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/047ea38d41d90d748bca812a43339632f52ba715
Web page

blk-throttle: Set BIO_THROTTLED when bio has been throttled - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24ba80efaf6e772f6132465fad08e20fb4767da7

Vendor Advisories for CVE-2022-49465(2)

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

Patch Availability(12)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-10-28ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-10-28ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1067 (5.15.0-1067.71) @ jammy2026-10-28ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-10-28ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1103.93) @ jammy2026-10-28ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1099.98) @ jammy2026-10-28ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1102.106) @ jammy2026-10-28ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-10-28ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1094.98) @ jammy2026-10-28ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1044.46) @ jammy2026-10-28ubuntu
redhatkernel-0:5.14.0-162.6.1.el9_12022-11-15redhat
linuxKernel @ 5.10.248 (fixes >=3.11.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 (48 versions)
  • every version up to 5.10.249-1: fixed in 5.10.249-1
—
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
—

Weakness Classification(1)

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

Additional Vendor Advisories

(10)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-49465?
CVE-2022-49465 is a high-severity vulnerability; its CVE record was published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: blk-throttle: Set BIO_THROTTLED when bio has been throttled 1.In current process, all bio will set the BIO_THROTTLED flag after __blk_throtl_bio(). 2.If bio needs to be throttled, it will start the timer and stop submit bio…
When was the CVE record for CVE-2022-49465 published?
The CVE record for CVE-2022-49465 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-49465 actively exploited?
CVE-2022-49465 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49465?
CVE-2022-49465 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49465?
A fix for CVE-2022-49465 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49465 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-49465

Explore →

Is Your Infrastructure Affected by CVE-2022-49465?

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

Book a Demo →Browse All CVEs