CVE-2014-7192

HIGHCVSS v2 · 10.010.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 13.0% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Elevated
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 13%CVSS v2: 10.0Exploit: Elevated riskExposed: 0

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

Eval injection vulnerability in index.js in the syntax-error package before 1.1.1 for Node.js 0.10.x, as used in IBM Rational Application Developer and other products, allows remote attackers to execute arbitrary code via a crafted file.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0(low)
EG Risk
66(Track)
EG Risk 66/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
13%
EPSS %ILE
96%
KEV
Not listed

Published

December 11, 2014

Last Modified

May 6, 2026

References (8)

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
syntax-error—1.1.1—

Data Freshness Timeline

(refreshed 10× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-26 14:50 UTCEPSS rescore
  2. 2026-07-26 13:52 UTCEG score recompute▲ 10.00
  3. 2026-07-24 14:13 UTCEPSS rescore
  4. 2026-07-23 14:14 UTCEPSS rescore
  5. 2026-07-23 01:14 UTCEG score recompute
  6. 2026-07-23 00:17 UTCEG score recompute
  7. 2026-07-22 21:56 UTCEG score recompute
  8. 2026-07-22 14:04 UTCEPSS rescore
  9. 2026-07-21 15:21 UTCEPSS rescore
  10. 2026-07-21 15:21 UTCEPSS rescore
  11. 2026-07-20 17:03 UTCEPSS rescore
  12. 2026-07-19 02:26 UTCEPSS rescore
  13. 2026-07-19 02:26 UTCEPSS rescore
  14. 2026-07-18 10:00 UTCEPSS rescore
  15. 2026-07-16 16:59 UTCEPSS rescore
  16. 2026-07-15 16:54 UTCEPSS rescore
  17. 2026-07-15 16:54 UTCEPSS rescore
  18. 2026-07-13 22:26 UTCEPSS rescore
  19. 2026-07-12 05:42 UTCEPSS rescore
  20. 2026-07-12 05:42 UTCEPSS rescore
  21. 2026-07-11 08:23 UTCEPSS rescore
  22. 2026-07-09 19:05 UTCEPSS rescore
  23. 2026-07-08 15:10 UTCEPSS rescore
  24. 2026-07-07 13:42 UTCEPSS rescore
  25. 2026-07-06 16:24 UTCEPSS rescore
Show 63 more
  1. 2026-07-06 02:20 UTCEPSS rescore
  2. 2026-07-05 02:26 UTCEPSS rescore
  3. 2026-07-04 06:27 UTCEPSS rescore
  4. 2026-07-01 15:02 UTCEPSS rescore
  5. 2026-07-01 15:02 UTCEPSS rescore
  6. 2026-06-30 23:19 UTCEPSS rescore
  7. 2026-06-30 23:19 UTCEPSS rescore
  8. 2026-06-29 14:02 UTCEPSS rescore
  9. 2026-06-28 04:53 UTCEPSS rescore
  10. 2026-06-28 04:53 UTCEPSS rescore
  11. 2026-06-27 03:05 UTCEPSS rescore
  12. 2026-06-25 13:47 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-24 14:02 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-23 21:30 UTCEPSS rescore
  18. 2026-06-22 14:22 UTCEPSS rescore
  19. 2026-06-22 14:22 UTCEPSS rescore
  20. 2026-06-21 01:57 UTCEPSS rescore
  21. 2026-06-19 19:23 UTCEPSS rescore
  22. 2026-06-18 17:49 UTCEPSS rescore
  23. 2026-06-18 17:49 UTCEPSS rescore
  24. 2026-06-17 17:49 UTCEPSS rescore
  25. 2026-06-17 17:49 UTCEPSS rescore
  26. 2026-06-16 17:50 UTCEPSS rescore
  27. 2026-06-16 17:49 UTCEPSS rescore
  28. 2026-06-16 17:49 UTCEPSS rescore
  29. 2026-06-12 23:08 UTCEPSS rescore
  30. 2026-06-11 13:57 UTCEPSS rescore
  31. 2026-06-10 22:15 UTCEPSS rescore
  32. 2026-06-07 15:22 UTCEPSS rescore
  33. 2026-06-06 13:45 UTCEPSS rescore
  34. 2026-06-06 13:45 UTCEPSS rescore
  35. 2026-06-05 22:44 UTCEPSS rescore
  36. 2026-06-05 06:08 UTCEPSS rescore
  37. 2026-06-05 06:08 UTCEPSS rescore
  38. 2026-06-04 13:09 UTCEPSS rescore
  39. 2026-06-04 13:09 UTCEPSS rescore
  40. 2026-06-02 20:10 UTCEPSS rescore
  41. 2026-06-02 20:10 UTCEPSS rescore
  42. 2026-05-31 22:28 UTCEPSS rescore
  43. 2026-05-31 22:28 UTCEPSS rescore
  44. 2026-05-31 00:14 UTCEPSS rescore
  45. 2026-05-31 00:14 UTCEPSS rescore
  46. 2026-05-29 13:41 UTCEPSS rescore
  47. 2026-05-28 14:36 UTCEG score recompute
  48. 2026-05-28 13:42 UTCEPSS rescore
  49. 2026-05-28 13:42 UTCEPSS rescore
  50. 2026-05-28 13:42 UTCEPSS rescore
  51. 2026-05-27 13:38 UTCEPSS rescore
  52. 2026-05-27 13:38 UTCEPSS rescore
  53. 2026-05-26 07:16 UTCEPSS rescore
  54. 2026-05-22 21:15 UTCEPSS rescore
  55. 2026-05-22 21:15 UTCEPSS rescore
  56. 2026-05-22 21:15 UTCEPSS rescore
  57. 2026-05-21 22:39 UTCEPSS rescore
  58. 2026-05-20 22:37 UTCEPSS rescore
  59. 2026-05-20 22:37 UTCEPSS rescore
  60. 2026-05-20 22:37 UTCEPSS rescore
  61. 2026-05-20 11:21 UTCEPSS rescore
  62. 2026-05-20 11:21 UTCEPSS rescore
  63. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-34090
    First seen Jul 16, 2014

    Node Browserify 4.2.0 - Remote Code Execution

    Open source ↗

Frequently asked(4)

What is CVE-2014-7192?
CVE-2014-7192 is a high vulnerability published on December 11, 2014. Eval injection vulnerability in index.js in the syntax-error package before 1.1.1 for Node.js 0.10.x, as used in IBM Rational Application Developer and other products, allows remote attackers to execute arbitrary code via a crafted file.
When was CVE-2014-7192 disclosed?
CVE-2014-7192 was first published in the National Vulnerability Database on December 11, 2014, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2014-7192 actively exploited?
CVE-2014-7192 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13% probability of exploitation in the next 30 days, which ranks it in the top 4.1% of all scored CVEs.
How do I remediate CVE-2014-7192?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2014-7192, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2014-7192

Explore →

Is Your Infrastructure Affected by CVE-2014-7192?

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

Start Free Scan →Browse All CVEs