CVE-2026-39823

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

CVE-2026-27142 fixed a vulnerability in which URLs were not correctly escaped inside of a tag's attribute. If the URL content were to insert ASCII whitespaces around the '=' rune inside of the attribute, the escaper would fail to similarly escape it, leading to XSS.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

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
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.3%
EPSS %ILE
24th
KEV
Not listed

Published

May 7, 2026

Last Modified

May 13, 2026

Advisory Details (4)

Auto-updated Jun 14, 2026
Patch available.
generic

GO-2026-4982 - Go Packages

https://pkg.go.dev/vuln/GO-2026-4982
generic

html/template: fix bypass for CVE-2026-27142 · Issue #78913 · golang/go · GitHub

https://go.dev/issue/78913

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatmulticluster-engine/hypershift-addon-rhel9-operator:17869120062026-08-19redhat
redhatrhosdt/opentelemetry-rhel9-operator:17857045472026-08-04redhat
redhatoadp/oadp-velero-rhel9:17840588222026-07-22redhat
redhatgolang1-25-main-1.25.11-2.hum12026-06-04redhat
redhatgolang1-26-main-1.26.4-2.hum12026-06-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 5 ecosystems)
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
golang-1.251.25.0-1 ... 1.25.9-1 (11 versions)
  • every version up to 1.25.10-1: fixed in 1.25.10-1
—
golang-1.261.26.0-1 ... 1.26~rc3-2 (9 versions)
  • every version up to 1.26.3-1: fixed in 1.26.3-1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.151.15.15-1 ... 1.15.9-6 (10 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.191.19.10-1 ... 1.19.9-1 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.241.24.12-1 ... 1.24.9-1 (10 versions)
  • every version on: no fix on record
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
stdlib—
  • every version up to 1.25.10: fixed in 1.25.10
  • 1.26.0-0 up to 1.26.3: fixed in 1.26.3
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-39823?
CVE-2026-39823 is a medium vulnerability published on May 7, 2026. CVE-2026-27142 fixed a vulnerability in which URLs were not correctly escaped inside of a <meta> tag's <content> attribute. If the URL content were to insert ASCII whitespaces around the '=' rune inside of the <content> attribute, the escaper would fail to similarly escape it, leading to XSS.
When was CVE-2026-39823 disclosed?
CVE-2026-39823 was first published on May 7, 2026, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-39823 actively exploited?
CVE-2026-39823 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-39823?
CVE-2026-39823 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-39823?
A fix for CVE-2026-39823 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-39823 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-39823

Explore →

Is Your Infrastructure Affected by CVE-2026-39823?

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