CVE-2026-52811

CRITICALPre-NVD 9.09.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-39082 (ENISA EUVD) · GHSA-89mr-xqfv-758m (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Gogs is an open source self-hosted Git service. Prior to 0.14.3, (*Repository).UploadRepoFiles checks for symlinks only on the leaf of the upload target (osx.IsSymlink(targetPath)). The siblings UpdateRepoFile, DeleteRepoFile, and GetDiffPreview use hasSymlinkInPath, which lstats every component — UploadRepoFiles is the lone outlier. An attacker with repo-write access plus a multipart upload whose filename contains a literal backslash (preserved by filepath.Base on Linux, then converted to / by pathx.Clean) redirects the write through a previously-committed directory symlink. iox.CopyFile opens the destination with os.Create (no O_NOFOLLOW), so the kernel follows the parent symlink and writes attacker bytes anywhere the gogs UID can write — ~git/.ssh/authorized_keys → SSH foothold, or .git/hooks/post-receive → next-push RCE. This vulnerability is fixed in 0.14.3.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.

EG Severity
9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 23, 2026

Last Modified

June 26, 2026

Advisory Details (4)

Auto-updated Jun 24, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

UploadRepoFiles writes outside repo working tree via committed parent sym · Advisory · gogs/gogs · GitHub

https://github.com/gogs/gogs/security/advisories/GHSA-89mr-xqfv-758m
GitHub release Patch Available

0.14.3

Patch available: gogs/gogs v0.14.3

https://github.com/gogs/gogs/releases/tag/v0.14.3
GitHub pull request

security: walk full upload path for symlinks

Fix merged in gogs/gogs PR #8332 on 2026-06-07 — awaiting tagged release

https://github.com/gogs/gogs/pull/8332
GitHub commit

commit 04cb8afbb01d (gogs/gogs)

Fix landed in gogs/gogs commit 04cb8afbb01d — awaiting tagged release

https://github.com/gogs/gogs/commit/04cb8afbb01d855454e59977a1cdbf522ea1db31

Vendor Advisories for CVE-2026-52811(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogogs.io/gogs @ 0.14.3 (fixes < 0.14.3)—ghsa

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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
gogs.io/gogs—
  • every version up to 0.14.3: fixed in 0.14.3
  • every version on: no fix on record
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 57× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 191 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 91 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-52811?
CVE-2026-52811 is a critical-severity vulnerability; its CVE record was published on June 23, 2026. Gogs is an open source self-hosted Git service. Prior to 0.14.3, (*Repository).UploadRepoFiles checks for symlinks only on the leaf of the upload target (osx.IsSymlink(targetPath)). The siblings UpdateRepoFile, DeleteRepoFile, and GetDiffPreview use hasSymlinkInPath, which lstats every component —…
When was the CVE record for CVE-2026-52811 published?
The CVE record for CVE-2026-52811 was published on June 23, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 26, 2026; the record at its source may have been updated since.
Is CVE-2026-52811 actively exploited?
CVE-2026-52811 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-52811?
CVE-2026-52811 has a CVSS base score of 9.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-52811?
A fix for CVE-2026-52811 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52811 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-52811

Explore →

Is Your Infrastructure Affected by CVE-2026-52811?

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

Book a Demo →Browse All CVEs