CVE-2026-105129

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-92051 (ENISA EUVD) · GHSA-7r4w-923q-fg62 (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.3%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

LaraDashboard before 1.4.8 contains an incorrect authorization vulnerability that allows authenticated users with only settings.view permission to read stored secrets through the settings API. Attackers can query GET /api/settings or /api/settings/{option_name} to retrieve plaintext AI provider API keys, mail credentials, passwords and tokens.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.3%
EPSS %ILE
23rd
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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: 60 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 public PoC (CISA Vulnrichment) · Automatable no (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)60 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 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

October 3, 2026

Last Modified

October 6, 2026

Advisory Details (9)

Auto-updated Oct 4, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
Web page

LaraDashboard before 1.4.8 Incorrect Authorization Exposes Secrets via Settings API | Advisories | VulnCheck

https://www.vulncheck.com/advisories/laradashboard-before-1.4.8-incorrect-authorization-exposes-secrets-via-settings-api
GitHub advisoryMentions a patch (unverified)

Raw Settings & Secret Dump via settings.view (extended by the new plaintext email_verification_api_key) · Advisory · laradashboard/laradashboard · GitHub

https://github.com/laradashboard/laradashboard/security/advisories/GHSA-xgmw-7ppx-v7hq
GitHub release Patch Available

Release v1.4.8

Patch available: laradashboard/laradashboard v1.4.8

https://github.com/laradashboard/laradashboard/releases/tag/v1.4.8
GitHub pull request Patch Available

Fix settings API secret disclosure (V-03)

Patch available: laradashboard/laradashboard v1.4.8 (PR #340 merged 2026-10-01)

https://github.com/laradashboard/laradashboard/pull/340
GitHub commit Patch Available

commit 532a10efd2cc (laradashboard/laradashboard)

Patch available: laradashboard/laradashboard v1.4.8 (contains commit 532a10efd2cc)

https://github.com/laradashboard/laradashboard/commit/532a10efd2cc1338ef3f59236f195df859b2dbe3
Web page

laradashboard/app/Policies/SettingPolicy.php at v1.4.2 · laradashboard/laradashboard · GitHub

https://github.com/laradashboard/laradashboard/blob/v1.4.2/app/Policies/SettingPolicy.php#L15-L34
Web page

laradashboard/app/Http/Resources/SettingResource.php at v1.4.2 · laradashboard/laradashboard · GitHub

https://github.com/laradashboard/laradashboard/blob/v1.4.2/app/Http/Resources/SettingResource.php#L17-L26
Web page

laradashboard/app/Http/Controllers/Api/SettingController.php at v1.4.2 · laradashboard/laradashboard · GitHub

https://github.com/laradashboard/laradashboard/blob/v1.4.2/app/Http/Controllers/Api/SettingController.php#L23-L50
Web page

GitHub - laradashboard/laradashboard: ⚡ Lara Dashboard - CMS by Laravel - All In One solution to start your Laravel Application from Basic to Enterprise. Manages Users, Roles, Permissions, Modules, Settings, Translations, Contents, Monitoring and every actions of your Laravel application. Complete solution for Laravel application with Tailwind, Livewire, Rest API, Unit-Tests and more. · GitHub

https://github.com/laradashboard/laradashboard

Vendor Advisories for CVE-2026-105129(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 8× in last 7d / 35× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-11-11 05:57 UTCEchelonGraph re-scored
  5. 2026-11-11 05:57 UTCGHSA enrichmentGHSA-7r4w-923q-fg62 · GitHub severity HIGH · GitHub CVSS 6.5
  6. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  9. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  13. 2026-11-04 00:39 UTCEchelonGraph re-scored
  14. 2026-11-04 00:39 UTCGHSA enrichmentGHSA-7r4w-923q-fg62 · GitHub severity HIGH · GitHub CVSS 6.5
  15. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  16. 2026-11-03 00:33 UTCEchelonGraph re-scored
  17. 2026-11-03 00:33 UTCGHSA enrichmentGHSA-7r4w-923q-fg62 · GitHub severity HIGH · GitHub CVSS 6.5
  18. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  19. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  20. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  21. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  22. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  23. 2026-10-29 14:53 UTCEchelonGraph re-scored
  24. 2026-10-29 14:53 UTCGHSA enrichmentGHSA-7r4w-923q-fg62 · GitHub severity HIGH · GitHub CVSS 6.5
  25. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
Show 50 more
  1. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-10-25 14:55 UTCEchelonGraph re-scored
  5. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  6. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-10-23 09:15 UTCEchelonGraph re-scored
  8. 2026-10-23 09:15 UTCGHSA enrichmentGHSA-7r4w-923q-fg62 · GitHub severity HIGH · GitHub CVSS 6.5
  9. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-10-18 05:09 UTCEchelonGraph re-scored
  15. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  16. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  18. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  19. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-10-12 16:40 UTCEchelonGraph re-scored
  21. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  22. 2026-10-11 20:15 UTCEchelonGraph re-scored
  23. 2026-10-11 18:36 UTCGHSA enrichmentGHSA-7r4w-923q-fg62 · GitHub severity HIGH · GitHub CVSS 6.5
  24. 2026-10-11 18:27 UTCEchelonGraph re-scored
  25. 2026-10-11 15:01 UTCEchelonGraph re-scored
  26. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  27. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  28. 2026-10-10 18:22 UTCEchelonGraph re-scored
  29. 2026-10-10 18:22 UTCGHSA enrichmentGHSA-7r4w-923q-fg62 · GitHub severity HIGH · GitHub CVSS 6.5
  30. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  31. 2026-10-09 18:08 UTCGHSA enrichmentGHSA-7r4w-923q-fg62 · GitHub severity HIGH · GitHub CVSS 6.5
  32. 2026-10-08 17:52 UTCEchelonGraph re-scored
  33. 2026-10-08 17:52 UTCGHSA enrichmentGHSA-7r4w-923q-fg62 · GitHub severity HIGH · GitHub CVSS 6.5
  34. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  35. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  36. 2026-10-07 17:33 UTCGHSA enrichmentGHSA-7r4w-923q-fg62 · GitHub severity HIGH · GitHub CVSS 6.5
  37. 2026-10-06 17:19 UTCEchelonGraph re-scored
  38. 2026-10-06 17:19 UTCGHSA enrichmentGHSA-7r4w-923q-fg62 · GitHub severity HIGH · GitHub CVSS 6.5
  39. 2026-10-06 17:02 UTCEchelonGraph re-scored
  40. 2026-10-06 17:02 UTCGHSA enrichmentGHSA-7r4w-923q-fg62 · GitHub severity HIGH · GitHub CVSS 6.5
  41. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  42. 2026-10-06 00:46 UTCEchelonGraph re-scored
  43. 2026-10-06 00:46 UTCGHSA enrichmentGHSA-7r4w-923q-fg62 · GitHub severity HIGH · GitHub CVSS 6.5
  44. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  45. 2026-10-05 00:34 UTCEchelonGraph re-scored
  46. 2026-10-05 00:33 UTCGHSA enrichmentGHSA-7r4w-923q-fg62 · GitHub severity HIGH · GitHub CVSS 6.5
  47. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  48. 2026-10-04 00:20 UTCEchelonGraph re-scored
  49. 2026-10-04 00:10 UTCEchelonGraph re-scoredFirst assessed: 6.5 MEDIUM
  50. 2026-10-04 00:10 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-105129?
CVE-2026-105129 is a medium-severity vulnerability; its CVE record was published on October 3, 2026. LaraDashboard before 1.4.8 contains an incorrect authorization vulnerability that allows authenticated users with only settings.view permission to read stored secrets through the settings API. Attackers can query GET /api/settings or /api/settings/{option_name} to retrieve plaintext AI provider API…
When was CVE-2026-105129 made public?
CVE-2026-105129 was made public on October 1, 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 October 3, 2026. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-105129 actively exploited?
CVE-2026-105129 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105129?
CVE-2026-105129 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-105129?
A fix for CVE-2026-105129 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-105129 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-105129?

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