CVE-2022-41853

CRITICALNVD 8.09.8
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-10-06. NVD baseline CVSS 8.0; sources differ by 1.8.

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

Also known asEUVD-2022-7043 (ENISA EUVD) · GHSA-77xx-rxvh-q682 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 5.1%CVSS: 8.0Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Those using java.sql.Statement or java.sql.PreparedStatement in hsqldb (HyperSQL DataBase) to process untrusted input may be vulnerable to a remote code execution attack. By default it is allowed to call any static method of any Java class in the classpath resulting in code execution. The issue can be prevented by updating to 2.7.1 or by setting the system property "hsqldb.method_class_names" to classes which are allowed to be called. For example, System.setProperty("hsqldb.method_class_names", "abc") or Java argument -Dhsqldb.method_class_names="abc" can be used. From version 2.7.1 all classes by default are not accessible except those in java.lang.Math and need to be manually enabled.

CVSS v3
8.0
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
5.1%
EPSS %ILE
92nd
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
5.1% 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

October 6, 2022

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Sep 20, 2026
Patch available.
Web page

[SECURITY] [DSA 5313-1] hsqldb security update

https://www.debian.org/security/2023/dsa-5313
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3234-1] hsqldb security update

https://lists.debian.org/debian-lts-announce/2022/12/msg00020.html

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhateap7-xalan-j2-0:2.7.1-26.redhat_00015.1.ep7.el72024-11-25redhat
redhateap7-xml-security-0:2.2.3-2.redhat_00001.1.el7eap2024-11-25redhat
redhathsqldb2023-05-03redhat
redhateap7-wildfly-http-client-0:1.1.16-1.Final_redhat_00002.1.el8eap2023-03-29redhat
redhatcom.h2database/h2:1.4.197.redhat-000042023-03-29redhat
redhateap7-wildfly-http-client-0:1.1.16-1.Final_redhat_00002.1.el9eap2023-03-29redhat
redhateap7-wildfly-http-client-0:1.1.16-1.Final_redhat_00002.1.el7eap2023-03-29redhat
redhathsqldb-1:1.8.0.10-13.el6_102022-11-21redhat
redhathsqldb-1:1.8.1.3-15.el7_92022-11-21redhat
mavenorg.hsqldb:hsqldb @ 2.7.1 (fixes < 2.7.1)—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

(6 across 6 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
hsqldb2.4.1-2
  • every version up to 2.4.1-2+deb10u1: fixed in 2.4.1-2+deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
hsqldb2.5.1-1
  • every version up to 2.5.1-1+deb11u1: fixed in 2.5.1-1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
hsqldb—
  • every version up to 2.7.1-1: fixed in 2.7.1-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
hsqldb—
  • every version up to 2.7.1-1: fixed in 2.7.1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
hsqldb—
  • every version up to 2.7.1-1: fixed in 2.7.1-1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.hsqldb:hsqldb1.8.0.10 ... 2.7.0 (22 versions)
  • every version up to 2.7.1: fixed in 2.7.1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 21× in last 7d / 54× 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 242 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 142 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCmbadanoiu/CVE-2022-41853
    Published Nov 24, 2023

    Research into CVE-2022-41853: Using static functions to obtian RCE via Java Deserialization & Remote Codebase Attack

    Open source ↗

Frequently asked(5)

What is CVE-2022-41853?
CVE-2022-41853 is a critical-severity vulnerability; its CVE record was published on October 6, 2022. Those using java.sql.Statement or java.sql.PreparedStatement in hsqldb (HyperSQL DataBase) to process untrusted input may be vulnerable to a remote code execution attack. By default it is allowed to call any static method of any Java class in the classpath resulting in code execution. The issue can…
When was CVE-2022-41853 made public?
CVE-2022-41853 was made public on July 26, 2021: that is the date its CVE record's CNA, Google LLC, gives for when the vulnerability was made public. The CVE record itself was published on October 6, 2022. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-41853 actively exploited?
CVE-2022-41853 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.1% probability of exploitation in the next 30 days (92nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-41853?
CVE-2022-41853 has a CVSS v3 base score of 8.0 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2022-41853?
A fix for CVE-2022-41853 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-41853 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-41853

Explore →

Is Your Infrastructure Affected by CVE-2022-41853?

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