CVE-2026-53932

HIGHPre-NVD 8.08.0
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.0 under the CNA's CVSS (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: cna:github_m
8.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 8.0Exploit: NoneExposed: 0

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

laravel-backup-restore has an OS Command Injection during database restore

Summary

A crafted backup archive can trigger OS command injection during database restore. The restore workflow extracts a ZIP archive, enumerates files under db-dumps, converts the dump path to an absolute path, and passes that path into database import commands that are built as shell command strings.

The dump filename is not shell-escaped before it is interpolated into commands such as:

  • mysql ... < {dumpFile}
  • gunzip -c {dumpFile} / gunzip < {dumpFile}
  • psql ... < {dumpFile}
  • sqlite3 ... < {dumpFile}

Because Illuminate\Support\Facades\Process::run(string) uses Symfony Process::fromShellCommandline(), shell metacharacters in the dump filename are interpreted by /bin/sh on Unix-like systems or by the platform shell on Windows.

Impact

If an attacker can cause an operator or automation to restore a malicious backup archive, the attacker can execute arbitrary shell commands as the PHP/Laravel application user on the system performing the restore. This can lead to application compromise, database credential disclosure, tampering with restored data, and further lateral movement depending on deployment permissions.

This is not about malicious SQL inside the dump. The command injection is carried in the ZIP entry filename under db-dumps, before the dump content is imported.

Patches

The vulnerability has been fixed in v1.9.4 of the package.

Workarounds

There is no configuration option that disables the vulnerable code path. Upgrading to the patched release is the only complete fix.

CVSS v3
8.0
EG Score
8.0(low)
EPSS
—
KEV
Not listed

Published

July 9, 2026

Last Modified

July 9, 2026

Vendor Advisories for CVE-2026-53932(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 13× in last 7d / 13× 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-07-15 16:38 UTCEG score recompute
  2. 2026-07-15 05:04 UTCEG score recompute
  3. 2026-07-14 17:29 UTCEG score recompute
  4. 2026-07-14 05:55 UTCEG score recompute
  5. 2026-07-13 18:20 UTCEG score recompute
  6. 2026-07-13 06:46 UTCEG score recompute
  7. 2026-07-12 19:12 UTCEG score recompute
  8. 2026-07-12 07:38 UTCEG score recompute
  9. 2026-07-11 20:04 UTCEG score recompute
  10. 2026-07-11 08:29 UTCEG score recompute
  11. 2026-07-10 20:55 UTCEG score recompute
  12. 2026-07-10 09:22 UTCEG score recompute
  13. 2026-07-09 21:46 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-53932?
CVE-2026-53932 is a high vulnerability published on July 9, 2026. laravel-backup-restore has an OS Command Injection during database restore Summary A crafted backup archive can trigger OS command injection during database restore. The restore workflow extracts a ZIP archive, enumerates files under db-dumps, converts the dump path to an absolute path, and passes…
When was CVE-2026-53932 disclosed?
CVE-2026-53932 was first published in the National Vulnerability Database on July 9, 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-53932?
CVE-2026-53932 has a CVSS v4.0 base score of 8.0 (CNA self-assessment; 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-53932?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53932, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-53932?

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

Start Free Scan →Browse All CVEs