CVE-2023-26155

HIGHNVD 7.37.3
EchelonGraph scoreMEDIUM confidence

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

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2023-10-14. NVD baseline CVSS 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated
7.3EG
EchelonGraph verdictPlan mitigationRemediate 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.2%CVSS: 7.3Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

All versions of the package node-qpdf are vulnerable to Command Injection such that the package-exported method encrypt() fails to sanitize its parameter input, which later flows into a sensitive command execution API. As a result, attackers may inject malicious commands once they can specify the input pdf file path.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
64
EG Risk 64/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)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
2.2%
EPSS %ILE
82nd
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.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
2.2% 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; 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).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

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

October 14, 2023

Last Modified

November 21, 2024

References (2)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmnode-qpdf—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)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
node-qpdf—
  • every version through 1.0.3: no fix on record
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 35× 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 91 of 190 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. 9 repeat rows among the latest 100 are merged into the row they repeat. The 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-26155?
CVE-2023-26155 is a high-severity vulnerability; its CVE record was published on October 14, 2023. All versions of the package node-qpdf are vulnerable to Command Injection such that the package-exported method encrypt() fails to sanitize its parameter input, which later flows into a sensitive command execution API. As a result, attackers may inject malicious commands once they can specify the…
When was the CVE record for CVE-2023-26155 published?
The CVE record for CVE-2023-26155 was published on October 14, 2023. 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-26155 actively exploited?
CVE-2023-26155 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.2% probability of exploitation in the next 30 days (82nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-26155?
CVE-2023-26155 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2023-26155?
No fix for CVE-2023-26155 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-26155

Explore →

Is Your Infrastructure Affected by CVE-2023-26155?

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

Book a Demo →Browse All CVEs