CVE-2026-76607

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd 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
10.0EG
EchelonGraph verdictPlan mitigationRemediate 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.4%CVSS: 10.0Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Joomla Extension - fabrikar.com - Missing ACL check in download element in Fabrik < 4.7.2.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation0.4% × 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 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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 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 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 22, 2026

Last Modified

August 26, 2026

Advisory Details (1)

Auto-updated Oct 7, 2026
No fix on record yet.
Web page

Fabrik - Joomla Custom Website Application Builder - Home

https://www.fabrikar.com/

Vendor Advisories for CVE-2026-76607(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 33× in last 7d / 181× 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 331 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 231 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-76607?
CVE-2026-76607 is a critical-severity vulnerability; its CVE record was published on August 22, 2026. Joomla Extension - fabrikar.com - Missing ACL check in download element in Fabrik < 4.7.2.
When was the CVE record for CVE-2026-76607 published?
The CVE record for CVE-2026-76607 was published on August 22, 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 August 26, 2026; the record at its source may have been updated since.
Is CVE-2026-76607 actively exploited?
CVE-2026-76607 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76607?
CVE-2026-76607 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76607?
No fix for CVE-2026-76607 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-76607 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-76607?

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

Book a Demo →Browse All CVEs