CVE-2022-35256

CRITICALNVD 6.59.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-12-06. NVD baseline CVSS 6.5; sources differ by 3.3.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 2.8%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

The llhttp parser in the http module in Node v18.7.0 does not correctly handle header fields that are not terminated with CLRF. This may result in HTTP Request Smuggling.

CVSS v3
6.5
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
2.8%
EPSS %ILE
86th
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
2.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

December 5, 2022

Last Modified

April 24, 2025

Advisory Details (3)

Auto-updated Oct 13, 2026
Patch available.

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntunodejs-doc (8.10.0~dfsg-2ubuntu0.4+esm4) @ bionic2026-10-23ubuntu
redhatnodejs:14-8060020230306170237.ad008a3a2023-04-12redhat
redhatnodejs:14-8040020230306170312.522a0ee42023-03-30redhat
redhatnodejs-1:16.18.1-3.el9_12023-01-23redhat
redhatnodejs:14-8070020221020110846.bd1311ed2022-11-08redhat
redhatnodejs:18-8070020221004121421.bd1311ed2022-11-08redhat
redhatrh-nodejs14-nodejs-0:14.20.1-2.el72022-10-19redhat
redhatnodejs-1:16.17.1-1.el9_02022-10-18redhat
redhatnodejs:16-8060020221007164523.ad008a3a2022-10-17redhat

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

(16 across 16 ecosystems)
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 14.20.1-r0: fixed in 14.20.1-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 14.20.1-r0: fixed in 14.20.1-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 16.17.1-r0: fixed in 16.17.1-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 16.17.1-r0: fixed in 16.17.1-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 16.17.1-r0: fixed in 16.17.1-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 16.17.1-r0: fixed in 16.17.1-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 16.17.1-r0: fixed in 16.17.1-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 16.17.1-r0: fixed in 16.17.1-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 16.17.1-r0: fixed in 16.17.1-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 16.17.1-r0: fixed in 16.17.1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 16.17.1-r0: fixed in 16.17.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 16.17.1-r0: fixed in 16.17.1-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs12.21.0~dfsg-5 ... 12.22.9~dfsg-1 (17 versions)
  • every version up to 12.22.12~dfsg-1~deb11u3: fixed in 12.22.12~dfsg-1~deb11u3
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 18.10.0+dfsg-1: fixed in 18.10.0+dfsg-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 18.10.0+dfsg-1: fixed in 18.10.0+dfsg-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 18.10.0+dfsg-1: fixed in 18.10.0+dfsg-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2022-35256?
CVE-2022-35256 is a critical-severity vulnerability; its CVE record was published on December 5, 2022. The llhttp parser in the http module in Node v18.7.0 does not correctly handle header fields that are not terminated with CLRF. This may result in HTTP Request Smuggling.
When was the CVE record for CVE-2022-35256 published?
The CVE record for CVE-2022-35256 was published on December 5, 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 24, 2025; the record at its source may have been updated since.
Is CVE-2022-35256 actively exploited?
CVE-2022-35256 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.8% probability of exploitation in the next 30 days (86th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-35256?
CVE-2022-35256 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2022-35256?
A fix for CVE-2022-35256 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-35256 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-35256

Explore →

Is Your Infrastructure Affected by CVE-2022-35256?

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