CVE-2026-103533

MEDIUMPre-NVD 4.14.1
EchelonGraph scoreMEDIUM confidence

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

Score 4.1 from GitHub Security Advisory (severity: LOW) published 2026-10-01. A secondary CVSS source baseline 4.1; 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-90463 (ENISA EUVD) · GHSA-h4ph-4xq3-682r (GitHub Security Advisories)Source: ENISA EUVD

4.1EG
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: 4.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

A vulnerability was found in David-Crty databasement up to 1.7.1. This impacts the function https:/github.com/David-Crty/databasement/pull/511 of the file app/Http/Requests/Api/V1/RestoreRequest.php of the component database-servers API Endpoint. The manipulation of the argument schema_name results in path traversal. The attack may be launched remotely. A high complexity level is associated with this attack. The exploitability is said to be difficult. The exploit has been made public and could be used. Upgrading to version 1.7.2 will fix this issue. You should upgrade the affected component.

CVSS v3
4.1
EG Score
4.1MEDIUMmedium confidence
EG Risk
34
EG Risk 34/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)
Severity41% × 45%
Impact severity (EG Severity): CVSS 4.1 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
21st
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 (4.1): severity, escalated by confirmed exploitation. This CVE's 4.1 is its impact severity (EG Severity), not escalated.

EG Severity
4.1 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-10-30). 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 1, 2026

Last Modified

October 1, 2026

Advisory Details (4)

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

GitHub - David-Crty/databasement: Self-hosted database backup manager with a web UI. Schedule, backup, and restore MySQL, PostgreSQL, MariaDB, Microsoft SQL Server, MongoDB, SQLite & Redis to S3, SFTP, Samba or local storage. SSH Tunnel support. · GitHub

https://github.com/David-Crty/databasement/
GitHub release Patch Available

v1.7.2

Patch available: David-Crty/databasement v1.7.2

https://github.com/David-Crty/databasement/releases/tag/v1.7.2
GitHub pull request Patch Available

Harden organization scoping and path validation

Patch available: David-Crty/databasement v1.7.2 (PR #511 merged 2026-08-04)

https://github.com/David-Crty/databasement/pull/511
GitHub advisoryMentions a patch (unverified)

Path Traversal to Remote Code Execution via SQLite Restore — Unvalidated `schema_name` Allows Webshell Write to Web Root · Advisory · David-Crty/databasement · GitHub

https://github.com/David-Crty/databasement/security/advisories/GHSA-x225-463f-pgww

Vendor Advisories for CVE-2026-103533(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 11× in last 7d / 61× 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.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-10-31 03:32 UTCEG score recompute
  4. 2026-10-31 03:32 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-10-29 14:51 UTCEG score recompute
  8. 2026-10-29 14:51 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  9. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-10-25 14:56 UTCEG score recompute
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  16. 2026-10-23 09:19 UTCEG score recompute
  17. 2026-10-23 09:19 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  18. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  19. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  20. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  21. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  22. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  23. 2026-10-18 05:09 UTCEG score recompute
  24. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 20th percentile
Show 49 more
  1. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-10-12 16:40 UTCEG score recompute
  5. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-12 01:27 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  7. 2026-10-11 20:15 UTCEG score recompute
  8. 2026-10-11 18:28 UTCEG score recompute
  9. 2026-10-11 15:01 UTCEG score recompute
  10. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-11 02:43 UTCEG score recompute
  12. 2026-10-11 02:43 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  13. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-10 03:59 UTCEG score recompute
  15. 2026-10-10 03:59 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  16. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-09 05:14 UTCEG score recompute
  18. 2026-10-09 05:14 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  19. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  20. 2026-10-08 06:30 UTCEG score recompute
  21. 2026-10-08 06:30 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  22. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-10-07 07:46 UTCEG score recompute
  24. 2026-10-07 07:46 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  25. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  26. 2026-10-06 09:02 UTCEG score recompute
  27. 2026-10-06 09:02 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  28. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  29. 2026-10-05 10:18 UTCEG score recompute
  30. 2026-10-05 10:18 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  31. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  32. 2026-10-04 11:34 UTCEG score recompute
  33. 2026-10-04 11:34 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  34. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  35. 2026-10-03 12:51 UTCEG score recompute
  36. 2026-10-03 12:51 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  37. 2026-10-02 14:07 UTCEG score recompute
  38. 2026-10-02 14:07 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  39. 2026-10-01 15:23 UTCEG score recompute
  40. 2026-10-01 15:23 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  41. 2026-10-01 15:22 UTCNVD updateCVSS v4 → 1.2
  42. 2026-10-01 14:42 UTCEG score recompute
  43. 2026-10-01 14:42 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  44. 2026-10-01 14:40 UTCMITRE cvelistV5CVSS v4 → 2.1
  45. 2026-10-01 03:35 UTCEG score recompute
  46. 2026-10-01 03:35 UTCGHSA enrichmentGHSA-h4ph-4xq3-682r · GitHub severity LOW · GitHub CVSS 4.1
  47. 2026-10-01 03:35 UTCNVD updateCVSS v4 → 1.2
  48. 2026-10-01 03:06 UTCEG score recomputeFirst assessed: 4.1 MEDIUM
  49. 2026-10-01 03:05 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-103533?
CVE-2026-103533 is a medium-severity vulnerability; its CVE record was published on October 1, 2026. A vulnerability was found in David-Crty databasement up to 1.7.1. This impacts the function https:/github.com/David-Crty/databasement/pull/511 of the file app/Http/Requests/Api/V1/RestoreRequest.php of the component database-servers API Endpoint. The manipulation of the argument schema_name results…
When was the CVE record for CVE-2026-103533 published?
The CVE record for CVE-2026-103533 was published on October 1, 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 October 1, 2026; the record at its source may have been updated since.
Is CVE-2026-103533 actively exploited?
CVE-2026-103533 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-103533?
CVE-2026-103533 has a CVSS base score of 4.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-103533?
A fix for CVE-2026-103533 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-103533 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-103533?

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