CVE-2026-25681

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

Score 6.1 from GitHub Security Advisory published 2026-05-26. NVD baseline CVSS 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.1Exploit: NoneExposed: 0

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

Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.

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

Published

May 26, 2026

Last Modified

May 29, 2026

Advisory Details (4)

Auto-updated Jun 15, 2026
No patch confirmed yet.
generic

GO-2026-5029 - Go Packages

https://pkg.go.dev/vuln/GO-2026-5029
generic
https://groups.google.com/g/golang-announce/c/iI-mYSI0lu8
generic

x/net/html: incorrect handling of character references in DOCTYPE nodes · Issue #79574 · golang/go · GitHub

https://go.dev/issue/79574
generic
https://go.dev/cl/781703

Vendor Advisories for CVE-2026-25681(20)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
golang.org/x/net—0.55.0—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 16× in last 7d / 59× 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 151 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-25681?
CVE-2026-25681 is a medium vulnerability published on May 26, 2026. Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.
When was CVE-2026-25681 disclosed?
CVE-2026-25681 was first published in the National Vulnerability Database on May 26, 2026, with the most recent update on May 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-25681 actively exploited?
CVE-2026-25681 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-25681?
CVE-2026-25681 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-25681?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25681, 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-25681

Explore →

Is Your Infrastructure Affected by CVE-2026-25681?

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

Start Free Scan →Browse All CVEs