CVE-2023-53192

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-09-15. 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 — 5 sources updated this week
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.4%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

vxlan: Fix nexthop hash size

The nexthop code expects a 31 bit hash, such as what is returned by fib_multipath_hash() and rt6_multipath_hash(). Passing the 32 bit hash returned by skb_get_hash() can lead to problems related to the fact that 'int hash' is a negative number when the MSB is set.

In the case of hash threshold nexthop groups, nexthop_select_path_hthr() will disproportionately select the first nexthop group entry. In the case of resilient nexthop groups, nexthop_select_path_res() may do an out of bounds access in nh_buckets[], for example: hash = -912054133 num_nh_buckets = 2 bucket_index = 65535

which leads to the following panic:

BUG: unable to handle page fault for address: ffffc900025910c8 PGD 100000067 P4D 100000067 PUD 10026b067 PMD 0 Oops: 0002 [#1] PREEMPT SMP KASAN NOPTI CPU: 4 PID: 856 Comm: kworker/4:3 Not tainted 6.5.0-rc2+ #34 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 Workqueue: ipv6_addrconf addrconf_dad_work RIP: 0010:nexthop_select_path+0x197/0xbf0 Code: c1 e4 05 be 08 00 00 00 4c 8b 35 a4 14 7e 01 4e 8d 6c 25 00 4a 8d 7c 25 08 48 01 dd e8 c2 25 15 ff 49 8d 7d 08 e8 39 13 15 ff <4d> 89 75 08 48 89 ef e8 7d 12 15 ff 48 8b 5d 00 e8 14 55 2f 00 85 RSP: 0018:ffff88810c36f260 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 00000000002000c0 RCX: ffffffffaf02dd77 RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffffc900025910c8 RBP: ffffc900025910c0 R08: 0000000000000001 R09: fffff520004b2219 R10: ffffc900025910cf R11: 31392d2068736168 R12: 00000000002000c0 R13: ffffc900025910c0 R14: 00000000fffef608 R15: ffff88811840e900 FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffc900025910c8 CR3: 0000000129d00000 CR4: 0000000000750ee0 PKRU: 55555554 Call Trace: ? __die+0x23/0x70 ? page_fault_oops+0x1ee/0x5c0 ? __pfx_is_prefetch.constprop.0+0x10/0x10 ? __pfx_page_fault_oops+0x10/0x10 ? search_bpf_extables+0xfe/0x1c0 ? fixup_exception+0x3b/0x470 ? exc_page_fault+0xf6/0x110 ? asm_exc_page_fault+0x26/0x30 ? nexthop_select_path+0x197/0xbf0 ? nexthop_select_path+0x197/0xbf0 ? lock_is_held_type+0xe7/0x140 vxlan_xmit+0x5b2/0x2340 ? __lock_acquire+0x92b/0x3370 ? __pfx_vxlan_xmit+0x10/0x10 ? __pfx___lock_acquire+0x10/0x10 ? __pfx_register_lock_class+0x10/0x10 ? skb_network_protocol+0xce/0x2d0 ? dev_hard_start_xmit+0xca/0x350 ? __pfx_vxlan_xmit+0x10/0x10 dev_hard_start_xmit+0xca/0x350 __dev_queue_xmit+0x513/0x1e20 ? __pfx___dev_queue_xmit+0x10/0x10 ? __pfx_lock_release+0x10/0x10 ? mark_held_locks+0x44/0x90 ? skb_push+0x4c/0x80 ? eth_header+0x81/0xe0 ? __pfx_eth_header+0x10/0x10 ? neigh_resolve_output+0x215/0x310 ? ip6_finish_output2+0x2ba/0xc90 ip6_finish_output2+0x2ba/0xc90 ? lock_release+0x236/0x3e0 ? ip6_mtu+0xbb/0x240 ? __pfx_ip6_finish_output2+0x10/0x10 ? find_held_lock+0x83/0xa0 ? lock_is_held_type+0xe7/0x140 ip6_finish_output+0x1ee/0x780 ip6_output+0x138/0x460 ? __pfx_ip6_output+0x10/0x10 ? __pfx___lock_acquire+0x10/0x10 ? __pfx_ip6_finish_output+0x10/0x10 NF_HOOK.constprop.0+0xc0/0x420 ? __pfx_NF_HOOK.constprop.0+0x10/0x10 ? ndisc_send_skb+0x2c0/0x960 ? __pfx_lock_release+0x10/0x10 ? __local_bh_enable_ip+0x93/0x110 ? lock_is_held_type+0xe7/0x140 ndisc_send_skb+0x4be/0x960 ? __pfx_ndisc_send_skb+0x10/0x10 ? mark_held_locks+0x65/0x90 ? find_held_lock+0x83/0xa0 ndisc_send_ns+0xb0/0x110 ? __pfx_ndisc_send_ns+0x10/0x10 addrconf_dad_work+0x631/0x8e0 ? lock_acquire+0x180/0x3f0 ? __pfx_addrconf_dad_work+0x10/0x10 ? mark_held_locks+0x24/0x90 process_one_work+0x582/0x9c0 ? __pfx_process_one_work+0x10/0x10 ? __pfx_do_raw_spin_lock+0x10/0x10 ? mark_held_locks+0x24/0x90 worker_thread+0x93/0x630 ? __kthread_parkme+0xdc/0x100 ? __pfx_worker_thread+0x10/0x10 kthread+0x1a5/0x1e0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x34/0x60 ---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.4% × 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.4%
EPSS %ILE
31st
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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). 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: 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.

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

September 15, 2025

Last Modified

August 5, 2026

Advisory Details (5)

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

vxlan: Fix nexthop hash size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0756384fb1bd38adb2ebcfd1307422f433a1d772
Web page

vxlan: Fix nexthop hash size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23c195ce6f4aec86e1c9e1ea1c800381c4b465c7
Web page

vxlan: Fix nexthop hash size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7b8717658dff8b471cbfc124bf9b5ca4229579ed
Web page

vxlan: Fix nexthop hash size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32ef2c0c6cf11a076f0280a7866b9abc47821e19
Web page

vxlan: Fix nexthop hash size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c650597647ecb318d02372277bdfd866c6829f78

Vendor Advisories for CVE-2023-53192(5)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-rt-0:5.14.0-284.158.1.rt14.443.el9_22026-02-25redhat
redhatkernel-0:5.14.0-284.158.1.el9_22026-02-25redhat
redhatkernel-0:5.14.0-70.165.1.el9_02026-02-11redhat
redhatkernel-rt-0:5.14.0-70.165.1.rt21.237.el9_02026-02-11redhat
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
linuxKernel @ 5.10.190 (fixes >=5.8.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 (33 versions)
  • every version up to 5.10.191-1: fixed in 5.10.191-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)
  • every version up to 6.1.52-1: fixed in 6.1.52-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.11-1: fixed in 6.4.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.11-1: fixed in 6.4.11-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 36× 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 92 of 189 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. 8 repeat rows among the latest 100 are merged into the row they repeat. The 97 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-53192?
CVE-2023-53192 is a high-severity vulnerability; its CVE record was published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: vxlan: Fix nexthop hash size The nexthop code expects a 31 bit hash, such as what is returned by fibmultipathhash() and rt6multipathhash(). Passing the 32 bit hash returned by skbgethash() can lead to problems related to the fact…
When was the CVE record for CVE-2023-53192 published?
The CVE record for CVE-2023-53192 was published on September 15, 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-2023-53192 actively exploited?
CVE-2023-53192 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53192?
CVE-2023-53192 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-53192?
A fix for CVE-2023-53192 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53192 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-2023-53192

Explore →

Is Your Infrastructure Affected by CVE-2023-53192?

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

Book a Demo →Browse All CVEs