CVE-2026-57570

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. 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: epss, secondary
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

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

backpack/crud provides Create, Read, Update & Delete (CRUD) functions for Backpack, a collection of Laravel packages that help users build custom administration panels. From 6.0.0 until 6.8.15 and 7.0.47, HasMany and MorphMany handling through attachManyRelation during CRUD create and update operations accepts submitted child primary keys without consistently restricting updates to records belonging to the current parent or permitted by the developer-defined relation scope. An authenticated low-privilege administrator who can edit a parent form exposing an affected multiple-relation field can cause unrelated child records to be reassigned, detached, nulled, or deleted across ownership or tenant boundaries. Exploitation requires related records that should not be attachable or removable by that administrator and the absence of additional application-level authorization around submitted relation values. This issue is distinct from earlier direct main-entity CRUD scoping fixes because it affects secondary models modified by relationship-saving logic. This issue is fixed in versions 6.8.15 and 7.0.47.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 20, 2026

Last Modified

September 14, 2026

Advisory Details (7)

Auto-updated Sep 14, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

7.0.47 🌈

Patch available: Laravel-Backpack/CRUD 7.0.47

https://github.com/Laravel-Backpack/CRUD/releases/tag/7.0.47
github_release Patch Available

6.8.15 🌈

Patch available: Laravel-Backpack/CRUD 6.8.15

https://github.com/Laravel-Backpack/CRUD/releases/tag/6.8.15
github_commit Patch Available

commit 24cfd2f61f3b (Laravel-Backpack/CRUD)

Patch available: Laravel-Backpack/CRUD 6.8.15 (contains commit 24cfd2f61f3b)

https://github.com/Laravel-Backpack/CRUD/commit/24cfd2f61f3b162c7bfd572368bc1b05c5f1fa75
github_commit Patch Available

commit 045ac00532ae (Laravel-Backpack/CRUD)

Patch available: Laravel-Backpack/CRUD 7.0.47 (contains commit 045ac00532ae)

https://github.com/Laravel-Backpack/CRUD/commit/045ac00532aebbd2ddcad260ba86f980f000a800
github_pr Patch Available

harden select relationships

Patch available: Laravel-Backpack/CRUD 6.8.15 (PR #6022 merged 2026-06-16)

https://github.com/Laravel-Backpack/CRUD/pull/6022
github_pr Patch Available

improve selectable relationships structure

Patch available: Laravel-Backpack/CRUD 7.0.47 (PR #6021 merged 2026-06-16)

https://github.com/Laravel-Backpack/CRUD/pull/6021
github Patch Available

HasMany/MorphMany relation fields allow cross-tenant record re-parenting (IDOR) via attachManyRelation · Advisory · Laravel-Backpack/CRUD · GitHub

https://github.com/Laravel-Backpack/CRUD/security/advisories/GHSA-42vx-43vc-x6pr

Vendor Advisories for CVE-2026-57570(1)

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

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
backpack/crud6.0.0 ... 6.8.9 (121 versions)6.8.15—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 9× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 12:18 UTCEG score recompute
  3. 2026-09-17 19:31 UTCEPSS rescore
  4. 2026-09-16 15:48 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-14 19:23 UTCEG score recompute
  8. 2026-09-14 18:28 UTCEG score recompute
  9. 2026-08-20 19:42 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-57570?
CVE-2026-57570 is a medium vulnerability published on August 20, 2026. backpack/crud provides Create, Read, Update & Delete (CRUD) functions for Backpack, a collection of Laravel packages that help users build custom administration panels. From 6.0.0 until 6.8.15 and 7.0.47, HasMany and MorphMany handling through attachManyRelation during CRUD create and update…
When was CVE-2026-57570 disclosed?
CVE-2026-57570 was first published in the National Vulnerability Database on August 20, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57570 actively exploited?
CVE-2026-57570 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.7% of all scored CVEs.
What is the CVSS score of CVE-2026-57570?
CVE-2026-57570 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-57570?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57570, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57570

Explore →

Is Your Infrastructure Affected by CVE-2026-57570?

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

Start Free Scan →Browse All CVEs