CVE-2026-80191

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-24. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GROWI applies its page-viewer permission check to attachment requests only when the request carries an authenticated user. retrieveAttachmentFromIdParam in apps/app/src/server/routes/attachment/get.ts guards the check with a condition requiring the user to be non-null, so a request that carries no session skips the check entirely and the handler returns the file. The routes reached this way, /attachment/:id and /download/:id, take the attachment identifier from the path, so an unauthenticated caller who has an attachment identifier receives the file regardless of whether the page owning it is private and regardless of whether that caller would be permitted to view the page. Identifiers can be retained by a user whose access was later removed, or recovered from anywhere the identifier was previously exposed. Version 8.0.2 runs the check for authenticated and unauthenticated requests alike, skipping it only where a valid share link has already bound the requested file to that link's page.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
49
EG Risk 49/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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

August 25, 2026

Last Modified

September 24, 2026

Advisory Details (5)

Auto-updated Aug 25, 2026
Patch available. Sources: github_pr, github_release.
Web page

GROWI before 8.0.2 Missing Authorization on Attachment Retrieval for Unauthenticated Requests | Advisories | VulnCheck

https://www.vulncheck.com/advisories/growi-before-8.0.2-missing-authorization-on-attachment-retrieval-for-unauthenticated-requests
GitHub release Patch Available

v8.0.2

Patch available: growilabs/growi v8.0.2

https://github.com/growilabs/growi/releases/tag/v8.0.2
Web page

growi/apps/app/src/server/routes/attachment/get.ts at v8.0.1 · growilabs/growi · GitHub

https://github.com/growilabs/growi/blob/v8.0.1/apps/app/src/server/routes/attachment/get.ts
GitHub pull request Patch Available

fix(attachment): Enforce page-viewer permission for guest requests too

Patch available: growilabs/growi v8.0.2 (PR #11756 merged 2026-08-25)

https://github.com/growilabs/growi/pull/11756
Web page

GitHub - growilabs/growi: :anchor: GROWI - Team collaboration software using markdown · GitHub

https://github.com/growilabs/growi

Vendor Advisories for CVE-2026-80191(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 83× 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 98 of 120 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 22 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-80191?
CVE-2026-80191 is a high-severity vulnerability; its CVE record was published on August 25, 2026. GROWI applies its page-viewer permission check to attachment requests only when the request carries an authenticated user. retrieveAttachmentFromIdParam in apps/app/src/server/routes/attachment/get.ts guards the check with a condition requiring the user to be non-null, so a request that carries no…
When was CVE-2026-80191 made public?
CVE-2026-80191 was made public on August 25, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 25, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-80191 actively exploited?
CVE-2026-80191 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80191?
CVE-2026-80191 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-80191?
A fix for CVE-2026-80191 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80191 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-80191

Explore →

Is Your Infrastructure Affected by CVE-2026-80191?

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

Book a Demo →Browse All CVEs