CVE-2026-105129

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 6.5Exploit: None knownExposed 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.5MEDIUMlow confidence
EG Risk
34
EG Risk 34/100CISA SSVC

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
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
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
—
EPSS %ILE
—
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or 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 (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 3, 2026

Last Modified

October 4, 2026

Advisory Details (9)

Auto-updated Oct 4, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
generic

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 Patch Available🟡 PoC Available

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_pr 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
generic

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
generic

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
generic

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
generic

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 3× in last 7d / 3× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-04 00:20 UTCEG score recompute
  2. 2026-10-04 00:10 UTCEG score recompute
  3. 2026-10-04 00:10 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-105129?
CVE-2026-105129 is a medium vulnerability 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 disclosed?
CVE-2026-105129 was first published on October 3, 2026, with the most recent update on October 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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.