CVE-2019-19391

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: MODERATE) published 2022-05-24. NVD baseline CVSS 9.1; sources differ by 0.0.

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

Also known asEUVD-2019-9012 (ENISA EUVD) · GHSA-756f-h55r-pvqq (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
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: 1.4%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In LuaJIT through 2.0.5, as used in Moonjit before 2.1.2 and other products, debug.getinfo has a type confusion issue that leads to arbitrary memory write or read operations, because certain cases involving valid stack levels and > options are mishandled. NOTE: The LuaJIT project owner states that the debug libary is unsafe by definition and that this is not a vulnerability. When LuaJIT was originally developed, the expectation was that the entire debug library had no security guarantees and thus it made no sense to assign CVEs. However, not all users of later LuaJIT derivatives share this perspective

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
42
EG Risk 42/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
1.4%
EPSS %ILE
72nd
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.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.4% 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 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 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

November 29, 2019

Last Modified

November 3, 2025

Advisory Details (2)

Auto-updated Aug 1, 2026
Patch available. Sources: github_pr.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4283-1] luajit security update

https://lists.debian.org/debian-lts-announce/2025/08/msg00022.html
GitHub pull request

debug.getinfo arbitrary memory read/write

Upstream fix in progress (PR #526 · LuaJIT/LuaJIT, state=closed)

https://github.com/LuaJIT/LuaJIT/pull/526

Vendor Advisories for CVE-2019-19391(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
luajit2.1.0~beta3+dfsg-5.3
  • every version up to 2.1.0~beta3+dfsg-5.3+deb11u1: fixed in 2.1.0~beta3+dfsg-5.3+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
luajit—
  • every version up to 2.1.0~beta3+git20210112+dfsg-2: fixed in 2.1.0~beta3+git20210112+dfsg-2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
luajit—
  • every version up to 2.1.0~beta3+git20210112+dfsg-2: fixed in 2.1.0~beta3+git20210112+dfsg-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
luajit—
  • every version up to 2.1.0~beta3+git20210112+dfsg-2: fixed in 2.1.0~beta3+git20210112+dfsg-2
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2019-19391?
CVE-2019-19391 is a critical-severity vulnerability; its CVE record was published on November 29, 2019. In LuaJIT through 2.0.5, as used in Moonjit before 2.1.2 and other products, debug.getinfo has a type confusion issue that leads to arbitrary memory write or read operations, because certain cases involving valid stack levels and > options are mishandled. NOTE: The LuaJIT project owner states that…
When was the CVE record for CVE-2019-19391 published?
The CVE record for CVE-2019-19391 was published on November 29, 2019. 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 3, 2025; the record at its source may have been updated since.
Is CVE-2019-19391 actively exploited?
CVE-2019-19391 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (72nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-19391?
CVE-2019-19391 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2019-19391?
A fix for CVE-2019-19391 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-19391 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-2019-19391

Explore →

Is Your Infrastructure Affected by CVE-2019-19391?

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

Book a Demo →Browse All CVEs