CVE-2026-42338

HIGHCVSS 8.16.1
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 83% 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
Trending — 4 sources updated this weekElevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

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

ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript. Prior to 10.1.1, Address6.group() and Address6.link() do not HTML-escape attacker-controlled content before embedding it in the HTML strings they return, and AddressError.parseMessage (emitted by the Address6 constructor for invalid input) can contain unescaped attacker-controlled content in one branch. An application that (1) passes untrusted input to Address6 and (2) renders the output of these methods, or the thrown error's parseMessage, as HTML (e.g. via innerHTML) is vulnerable to cross-site scripting. This vulnerability is fixed in 10.1.1.

CVSS v3
8.1
EG Score
6.1(medium)
EPSS
37.6%
KEV
Not listed

Published

May 12, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated Jun 16, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

XSS in Address6 HTML-emitting methods · Advisory · beaugunderson/ip-address · GitHub

https://github.com/beaugunderson/ip-address/security/advisories/GHSA-v2v4-37r5-5v8g

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
ip-address10.1.1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 52× 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 106 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42338?
CVE-2026-42338 is a high vulnerability published on May 12, 2026. ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript. Prior to 10.1.1, Address6.group() and Address6.link() do not HTML-escape attacker-controlled content before embedding it in the HTML strings they return, and AddressError.parseMessage (emitted by the…
When was CVE-2026-42338 disclosed?
CVE-2026-42338 was first published in the National Vulnerability Database on May 12, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42338 actively exploited?
CVE-2026-42338 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 37.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42338?
CVE-2026-42338 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 6.1.
How do I remediate CVE-2026-42338?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42338, 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-2026-42338

Explore →

Is Your Infrastructure Affected by CVE-2026-42338?

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