CVE-2022-49763

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-05-01. 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 — 3 sources updated this week

Also known asEUVD-2025-12995 (ENISA EUVD) · GHSA-h4jf-hv6r-g8qq (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:

ntfs: fix use-after-free in ntfs_attr_find()

Patch series "ntfs: fix bugs about Attribute", v2.

This patchset fixes three bugs relative to Attribute in record:

Patch 1 adds a sanity check to ensure that, attrs_offset field in first mft record loading from disk is within bounds.

Patch 2 moves the ATTR_RECORD's bounds checking earlier, to avoid dereferencing ATTR_RECORD before checking this ATTR_RECORD is within bounds.

Patch 3 adds an overflow checking to avoid possible forever loop in ntfs_attr_find().

Without patch 1 and patch 2, the kernel triggersa KASAN use-after-free detection as reported by Syzkaller.

Although one of patch 1 or patch 2 can fix this, we still need both of them. Because patch 1 fixes the root cause, and patch 2 not only fixes the direct cause, but also fixes the potential out-of-bounds bug.

This patch (of 3):

Syzkaller reported use-after-free read as follows: ================================================================== BUG: KASAN: use-after-free in ntfs_attr_find+0xc02/0xce0 fs/ntfs/attrib.c:597 Read of size 2 at addr ffff88807e352009 by task syz-executor153/3607

[...] Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:317 [inline] print_report.cold+0x2ba/0x719 mm/kasan/report.c:433 kasan_report+0xb1/0x1e0 mm/kasan/report.c:495 ntfs_attr_find+0xc02/0xce0 fs/ntfs/attrib.c:597 ntfs_attr_lookup+0x1056/0x2070 fs/ntfs/attrib.c:1193 ntfs_read_inode_mount+0x89a/0x2580 fs/ntfs/inode.c:1845 ntfs_fill_super+0x1799/0x9320 fs/ntfs/super.c:2854 mount_bdev+0x34d/0x410 fs/super.c:1400 legacy_get_tree+0x105/0x220 fs/fs_context.c:610 vfs_get_tree+0x89/0x2f0 fs/super.c:1530 do_new_mount fs/namespace.c:3040 [inline] path_mount+0x1326/0x1e20 fs/namespace.c:3370 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount fs/namespace.c:3568 [inline] __x64_sys_mount+0x27f/0x300 fs/namespace.c:3568 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+0x63/0xcd [...]

The buggy address belongs to the physical page: page:ffffea0001f8d400 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x7e350 head:ffffea0001f8d400 order:3 compound_mapcount:0 compound_pincount:0 flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000010200 0000000000000000 dead000000000122 ffff888011842140 raw: 0000000000000000 0000000000040004 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff88807e351f00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff88807e351f80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff88807e352000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff88807e352080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff88807e352100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ==================================================================

Kernel will loads $MFT/$DATA's first mft record in ntfs_read_inode_mount().

Yet the problem is that after loading, kernel doesn't check whether attrs_offset field is a valid value.

To be more specific, if attrs_offset field is larger than bytes_allocated field, then it may trigger the out-of-bounds read bug(reported as use-after-free bug) in ntfs_attr_find(), when kernel tries to access the corresponding mft record's attribute.

This patch solves it by adding the sanity check between attrs_offset field and bytes_allocated field, after loading the first mft record.

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
12th
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

May 1, 2025

Last Modified

August 5, 2026

Advisory Details (8)

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

ntfs: fix use-after-free in ntfs_attr_find() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ntfs: fix use-after-free in ntfs_attr_find() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4863f815463034f588a035cfd99cdca97a4f1069
Web page

ntfs: fix use-after-free in ntfs_attr_find() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5330c423b86263ac7883fef0260b9e2229cb531e
Web page

ntfs: fix use-after-free in ntfs_attr_find() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ntfs: fix use-after-free in ntfs_attr_find() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/266bd5306286316758e6246ea0345133427b0f62
Web page

ntfs: fix use-after-free in ntfs_attr_find() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ntfs: fix use-after-free in ntfs_attr_find() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ntfs: fix use-after-free in ntfs_attr_find() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/79f3ac7dcd12c05b7539239a4c6fa229a50d786c

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 4.9.334 (fixes >=2.6.12)—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 (22 versions)
  • every version up to 5.10.158-1: fixed in 5.10.158-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.10-1: fixed in 6.0.10-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.10-1: fixed in 6.0.10-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.10-1: fixed in 6.0.10-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-49763?
CVE-2022-49763 is a high-severity vulnerability; its CVE record was published on May 1, 2025. In the Linux kernel, the following vulnerability has been resolved: ntfs: fix use-after-free in ntfs_attr_find() Patch series "ntfs: fix bugs about Attribute", v2. This patchset fixes three bugs relative to Attribute in record: Patch 1 adds a sanity check to ensure that, attrs_offset field in first…
When was the CVE record for CVE-2022-49763 published?
The CVE record for CVE-2022-49763 was published on May 1, 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-49763 actively exploited?
CVE-2022-49763 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49763?
CVE-2022-49763 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49763?
A fix for CVE-2022-49763 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-49763

Explore →

Is Your Infrastructure Affected by CVE-2022-49763?

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

Book a Demo →Browse All CVEs