CVE-2026-75827

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-17. A secondary CVSS source baseline 8.8; 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 weekElevated

Also known asEUVD-2026-60591 (ENISA EUVD) · GHSA-f8wv-xp27-6gq7 (GitHub Security Advisories) · GHSA-fwwx-3362-3947 (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Grav before 2.0.15 contains an arbitrary file write vulnerability in the Blueprint dynamic-data bare-function validation that uses an incomplete denylist instead of a positive allowlist. Attackers with page-edit or blueprint-config access can invoke the error_log function through a data directive to append PHP payloads to web-accessible files, achieving remote code execution.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
58th
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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, Track* at medium and Attend at high mission impact.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, Track* at medium and Attend at high mission impact.

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

Exploitation public PoC (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

August 18, 2026

Last Modified

October 22, 2026

Advisory Details (2)

Auto-updated Aug 18, 2026
Patch available. Sources: github.
Web page

Grav before 2.0.15 Arbitrary File Write via error_log | Advisories | VulnCheck

https://www.vulncheck.com/advisories/grav-before-arbitrary-file-write-via-error-log
GitHub advisoryMentions a patch (unverified)

Blueprint dynamic-data bare-function branch is denylist-gated and omits error_log, giving arbitrary file write · Advisory · getgrav/grav · GitHub

https://github.com/getgrav/grav/security/advisories/GHSA-f8wv-xp27-6gq7

Vendor Advisories for CVE-2026-75827(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
composergetgrav/grav @ 2.0.15 (fixes <= 2.0.14)—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)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
getgrav/grav0.8.0 ... 2.0.9 (349 versions)
  • every version up to 2.0.15: fixed in 2.0.15
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 48× 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 190 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 90 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-75827?
CVE-2026-75827 is a high-severity vulnerability; its CVE record was published on August 18, 2026. Grav before 2.0.15 contains an arbitrary file write vulnerability in the Blueprint dynamic-data bare-function validation that uses an incomplete denylist instead of a positive allowlist. Attackers with page-edit or blueprint-config access can invoke the error_log function through a data directive…
When was CVE-2026-75827 made public?
CVE-2026-75827 was made public on August 3, 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 18, 2026. EchelonGraph's copy of the record carries a last-modified date of October 22, 2026; the record at its source may have been updated since.
Is CVE-2026-75827 actively exploited?
CVE-2026-75827 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-75827?
CVE-2026-75827 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-75827?
A fix for CVE-2026-75827 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-75827 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-75827

Explore →

Is Your Infrastructure Affected by CVE-2026-75827?

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