CVE-2026-42518

CVE-2026-42518 is a high-severity vulnerability with a CVSS 4.0 base score of 8.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-321.

Key facts

Description

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.

Frequently asked questions

What is CVE-2026-42518?
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.
How severe is CVE-2026-42518?
CVE-2026-42518 has a CVSS 4.0 base score of 8.7, rated high severity.
Is CVE-2026-42518 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (12th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-42518?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-42518 have an EU (EUVD) identifier?
Yes. CVE-2026-42518 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-26204.
When was CVE-2026-42518 published?
CVE-2026-42518 was published on 2026-04-29 and last updated on 2026-06-17.

References

Other CWE-321 vulnerabilities

Browse all CWE-321 vulnerabilities →