CVE-2022-4116

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-11-22. NVD baseline CVSS 9.8; sources differ by 0.0.

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

Also known asEUVD-2022-7338 (ENISA EUVD) · GHSA-g56w-cwg4-hxx9 (GitHub Security Advisories)Source: ENISA EUVD

9.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: 33%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

A vulnerability was found in quarkus. This security flaw happens in Dev UI Config Editor which is vulnerable to drive-by localhost attacks leading to remote code execution.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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
33%
EPSS %ILE
98th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
33% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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

November 22, 2022

Last Modified

April 29, 2025

Advisory Details (1)

Auto-updated Oct 10, 2026
Patch available. Sources: redhat.
Red HatMentions a patch (unverified)

CVE-2022-4116 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2022-4116

Vendor Advisories for CVE-2022-4116(2)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpatch2022-12-14redhat
redhatquarkus_dev_ui2022-12-13redhat
mavenio.quarkus:quarkus-vertx-http-deployment @ 2.13.5.Final (fixes < 2.13.5.Final)—ghsa
mavenio.quarkus:quarkus-vertx-http-deployment @ 2.14.2.Final (fixes >= 2.14.0, < 2.14.2.Final)—ghsa

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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
io.quarkus:quarkus-vertx-http-deployment0.23.0 ... 2.9.2.Final (170 versions)
  • 2.14.0 up to 2.14.2.Final: fixed in 2.14.2.Final
  • every version up to 2.13.5.Final: fixed in 2.13.5.Final
—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

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 19× in last 7d / 70× 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 256 rows 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. None are among the latest 100 rows. The 156 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2022-4116?
CVE-2022-4116 is a critical-severity vulnerability; its CVE record was published on November 22, 2022. A vulnerability was found in quarkus. This security flaw happens in Dev UI Config Editor which is vulnerable to drive-by localhost attacks leading to remote code execution.
When was the CVE record for CVE-2022-4116 published?
The CVE record for CVE-2022-4116 was published on November 22, 2022. 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 April 29, 2025; the record at its source may have been updated since.
Is CVE-2022-4116 actively exploited?
CVE-2022-4116 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-4116?
CVE-2022-4116 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-4116?
A fix for CVE-2022-4116 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-4116 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-4116

Explore →

Is Your Infrastructure Affected by CVE-2022-4116?

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