CVE-2022-49142

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 published 2025-10-15. 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-55082 (ENISA EUVD) · GHSA-62rq-h65m-5cww (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.6%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net: preserve skb_end_offset() in skb_unclone_keeptruesize()

syzbot found another way to trigger the infamous WARN_ON_ONCE(delta < len) in skb_try_coalesce() [1]

I was able to root cause the issue to kfence.

When kfence is in action, the following assertion is no longer true:

int size = xxxx; void *ptr1 = kmalloc(size, gfp); void *ptr2 = kmalloc(size, gfp);

if (ptr1 && ptr2) ASSERT(ksize(ptr1) == ksize(ptr2));

We attempted to fix these issues in the blamed commits, but forgot that TCP was possibly shifting data after skb_unclone_keeptruesize() has been used, notably from tcp_retrans_try_collapse().

So we not only need to keep same skb->truesize value, we also need to make sure TCP wont fill new tailroom that pskb_expand_head() was able to get from a addr = kmalloc(...) followed by ksize(addr)

Split skb_unclone_keeptruesize() into two parts:

1) Inline skb_unclone_keeptruesize() for the common case, when skb is not cloned.

2) Out of line __skb_unclone_keeptruesize() for the 'slow path'.

WARNING: CPU: 1 PID: 6490 at net/core/skbuff.c:5295 skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295 Modules linked in: CPU: 1 PID: 6490 Comm: syz-executor161 Not tainted 5.17.0-rc4-syzkaller-00229-g4f12b742eb2b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:skb_try_coalesce+0x1235/0x1560 net/core/skbuff.c:5295 Code: bf 01 00 00 00 0f b7 c0 89 c6 89 44 24 20 e8 62 24 4e fa 8b 44 24 20 83 e8 01 0f 85 e5 f0 ff ff e9 87 f4 ff ff e8 cb 20 4e fa <0f> 0b e9 06 f9 ff ff e8 af b2 95 fa e9 69 f0 ff ff e8 95 b2 95 fa RSP: 0018:ffffc900063af268 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 00000000ffffffd5 RCX: 0000000000000000 RDX: ffff88806fc05700 RSI: ffffffff872abd55 RDI: 0000000000000003 RBP: ffff88806e675500 R08: 00000000ffffffd5 R09: 0000000000000000 R10: ffffffff872ab659 R11: 0000000000000000 R12: ffff88806dd554e8 R13: ffff88806dd9bac0 R14: ffff88806dd9a2c0 R15: 0000000000000155 FS: 00007f18014f9700(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020002000 CR3: 000000006be7a000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: tcp_try_coalesce net/ipv4/tcp_input.c:4651 [inline] tcp_try_coalesce+0x393/0x920 net/ipv4/tcp_input.c:4630 tcp_queue_rcv+0x8a/0x6e0 net/ipv4/tcp_input.c:4914 tcp_data_queue+0x11fd/0x4bb0 net/ipv4/tcp_input.c:5025 tcp_rcv_established+0x81e/0x1ff0 net/ipv4/tcp_input.c:5947 tcp_v4_do_rcv+0x65e/0x980 net/ipv4/tcp_ipv4.c:1719 sk_backlog_rcv include/net/sock.h:1037 [inline] __release_sock+0x134/0x3b0 net/core/sock.c:2779 release_sock+0x54/0x1b0 net/core/sock.c:3311 sk_wait_data+0x177/0x450 net/core/sock.c:2821 tcp_recvmsg_locked+0xe28/0x1fd0 net/ipv4/tcp.c:2457 tcp_recvmsg+0x137/0x610 net/ipv4/tcp.c:2572 inet_recvmsg+0x11b/0x5e0 net/ipv4/af_inet.c:850 sock_recvmsg_nosec net/socket.c:948 [inline] sock_recvmsg net/socket.c:966 [inline] sock_recvmsg net/socket.c:962 [inline] ____sys_recvmsg+0x2c4/0x600 net/socket.c:2632 ___sys_recvmsg+0x127/0x200 net/socket.c:2674 __sys_recvmsg+0xe2/0x1a0 net/socket.c:2704 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae

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.6% × 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.6%
EPSS %ILE
50th
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.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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

October 3, 2026

Advisory Details (5)

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

net: preserve skb_end_offset() in skb_unclone_keeptruesize() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: preserve skb_end_offset() in skb_unclone_keeptruesize() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: preserve skb_end_offset() in skb_unclone_keeptruesize() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91c118727432a5d776d5fe86e0cf8eb1289ac1fc
Web page

net: preserve skb_end_offset() in skb_unclone_keeptruesize() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2b88cba55883eaafbc9b7cbff0b2c7cdba71ed01
Web page

net: preserve skb_end_offset() in skb_unclone_keeptruesize() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23629b673b780d967b88a850b1518cf0f0ffc6aa

Vendor Advisories for CVE-2022-49142(2)

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-162.6.1.el9_12022-11-15redhat
linuxKernel @ 5.15.33 (fixes >=5.12.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.17.3-1: fixed in 5.17.3-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—

Data Freshness Timeline

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

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2022-49142?
CVE-2022-49142 is a medium-severity vulnerability; its CVE record was published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: net: preserve skb_end_offset() in skb_unclone_keeptruesize() syzbot found another way to trigger the infamous WARN_ON_ONCE(delta < len) in skb_try_coalesce() [1] I was able to root cause the issue to kfence. When kfence is in…
When was the CVE record for CVE-2022-49142 published?
The CVE record for CVE-2022-49142 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 October 3, 2026; the record at its source may have been updated since.
Is CVE-2022-49142 actively exploited?
CVE-2022-49142 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49142?
CVE-2022-49142 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49142?
A fix for CVE-2022-49142 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49142 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-49142

Explore →

Is Your Infrastructure Affected by CVE-2022-49142?

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

Book a Demo →Browse All CVEs