CVE-2026-42518

HIGHNVD 8.78.7
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

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

This vulnerability exists in e-Sushrut due to disclosure of sensitive information and hardcoded AES encryption keys in client-side JavaScript. An unauthenticated remote attacker could exploit this vulnerability by accessing the client-side code to extract sensitive information and cryptographic keys.

Successful exploitation of this vulnerability could lead to exposure of sensitive data and compromise of cryptographic protections on the targeted system.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
39(Track)
EG Risk 39/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
Severity87% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

April 29, 2026

Last Modified

April 29, 2026

Advisory Details (1)

Auto-updated Apr 29, 2026
No patch confirmed yet.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 25× 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.

Showing the most recent 100 of 191 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42518?
CVE-2026-42518 is a high vulnerability published on April 29, 2026. This vulnerability exists in e-Sushrut due to disclosure of sensitive information and hardcoded AES encryption keys in client-side JavaScript. An unauthenticated remote attacker could exploit this vulnerability by accessing the client-side code to extract sensitive information and cryptographic…
When was CVE-2026-42518 disclosed?
CVE-2026-42518 was first published in the National Vulnerability Database on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42518 actively exploited?
CVE-2026-42518 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.6% of all scored CVEs.
What is the CVSS score of CVE-2026-42518?
CVE-2026-42518 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-42518?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42518, 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

Explore the affected products and dependency analysis for CVE-2026-42518

Explore →

Is Your Infrastructure Affected by CVE-2026-42518?

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