CVE-2026-39822

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-08. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

On Unix systems, opening a file in an os.Root improperly follows symlinks to locations outside of the Root when the final path component of the a path is a symbolic link and the path ends in /. For example, 'root.Open("symlink/")' will open "symlink" even when "symlink" is a symbolic link pointing outside of the root.

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

Published

July 8, 2026

Last Modified

July 13, 2026

Advisory Details (4)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

GO-2026-4970 - Go Packages

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

os: Root escape via symlink plus trailing slash (CVE-2026-39822) · Issue #79005 · golang/go · GitHub

https://go.dev/issue/79005

Patch Availability(14)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhosdt/opentelemetry-rhel9-operator:17866351752026-08-13redhat
redhatquay/quay-rhel8:17863950652026-08-11redhat
redhatquay/quay-rhel8:17861706352026-08-10redhat
redhatquay/quay-rhel8:17859500042026-08-05redhat
redhatadvanced-cluster-security/rhacs-main-rhel9:17854158682026-07-30redhat
redhatrhosdt/tempo-rhel9-operator:17847757822026-07-23redhat
redhatpodman-6:5.8.2-5.el9_82026-07-13redhat
redhatgo-toolset:rhel8-8100020260710105056.a3795dee2026-07-13redhat
redhatbuildah-2:1.43.1-4.el10_22026-07-13redhat
redhatbuildah-2:1.43.1-4.el9_82026-07-13redhat
redhatgolang-0:1.26.5-1.el10_22026-07-09redhat
redhatgolang-0:1.26.5-1.el9_82026-07-09redhat
redhatgolang1-25-main-1.25.12-0.1.hum12026-07-08redhat
redhatgolang1-26-main-1.26.5-0.1.hum12026-07-08redhat

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

(5 across 3 ecosystems)
Debian:14(3)
PackageVulnerable rangeFixed inDependents
golang-1.251.25.0-1 ... 1.25.9-1 (17 versions)1.25.12-1
golang-1.261.26.0-1 ... 1.26~rc3-2 (15 versions)1.26.5-1
golang-1.271.27~rc1-11.27~rc2-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-1.241.24.12-1 ... 1.24.9-1 (10 versions)
Go(1)
PackageVulnerable rangeFixed inDependents
stdlib1.27.0-rc.2

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-39822?
CVE-2026-39822 is a high vulnerability published on July 8, 2026. On Unix systems, opening a file in an os.Root improperly follows symlinks to locations outside of the Root when the final path component of the a path is a symbolic link and the path ends in /. For example, 'root.Open("symlink/")' will open "symlink" even when "symlink" is a symbolic link pointing…
When was CVE-2026-39822 disclosed?
CVE-2026-39822 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 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-39822 actively exploited?
CVE-2026-39822 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 86.1% of all scored CVEs.
What is the CVSS score of CVE-2026-39822?
CVE-2026-39822 has a CVSS v3.1 base score of 7.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-39822?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39822, 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-39822

Explore →

Is Your Infrastructure Affected by CVE-2026-39822?

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