CVE-2026-71415

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 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
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

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

Kirby is an open-source content management system. From 5.0.0 until 5.5.2, Kirby's REST API chunk upload handler in src/Api/Upload.php did not run the relevant upload authorization preflight in Kirby\Api\Upload::process() before Kirby\Api\Upload::processChunk() persisted chunk data. An authenticated user with the access.panel permission enabled but with files.create, files.replace, and user/users.update permissions disabled could submit requests with an Upload-Length header and leave unfinished chunks in site/cache/.uploads for 24 hours. Repeating this process could consume attacker-controlled temporary storage, prevent other users from uploading files, or prevent site logic from storing data, although final permission checks still prevented unauthorized files from reaching the content or site/accounts directories. This issue is fixed in version 5.5.2.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 31, 2026

Last Modified

September 8, 2026

Advisory Details (4)

Auto-updated Aug 31, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

5.5.2

Patch available: getkirby/kirby 5.5.2

https://github.com/getkirby/kirby/releases/tag/5.5.2
github_commit Patch Available

commit 37e206f3ed40 (getkirby/kirby)

Patch available: getkirby/kirby 5.5.2 (contains commit 37e206f3ed40)

https://github.com/getkirby/kirby/commit/37e206f3ed40ad3fab2e47e055ccb19e9c207dab
github_pr Patch Available

5.5.2

Patch available: getkirby/kirby 5.5.2 (PR #8296 merged 2026-07-15)

https://github.com/getkirby/kirby/pull/8296
github Patch Available

File upload permissions are not checked during processing of chunk data · Advisory · getkirby/kirby · GitHub

https://github.com/getkirby/kirby/security/advisories/GHSA-67mx-6wf2-92xp

Vendor Advisories for CVE-2026-71415(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
getkirby/cms5.0.0 ... 5.5.1 (28 versions)5.5.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 35× 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-19 01:26 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 23:58 UTCEG score recompute
  4. 2026-09-16 21:51 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 09:07 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 07:24 UTCEG score recompute
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-13 16:55 UTCEG score recompute
  11. 2026-09-12 15:27 UTCEG score recompute
  12. 2026-09-12 15:02 UTCEPSS rescore
  13. 2026-09-12 02:40 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 13:56 UTCEG score recompute
  16. 2026-09-10 12:29 UTCEG score recompute
  17. 2026-09-10 09:35 UTCEPSS rescore
  18. 2026-09-09 09:56 UTCEG score recompute
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-08 03:40 UTCEG score recompute
  21. 2026-09-06 23:53 UTCEG score recompute
  22. 2026-09-06 13:48 UTCEPSS rescore
  23. 2026-09-05 22:22 UTCEG score recompute
  24. 2026-09-04 20:55 UTCEG score recompute
  25. 2026-09-04 08:07 UTCEG score recompute
Show 10 more
  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-03 19:23 UTCEG score recompute
  3. 2026-09-03 18:37 UTCEG score recompute
  4. 2026-09-03 00:24 UTCEG score recompute
  5. 2026-09-02 14:12 UTCEPSS rescore
  6. 2026-09-01 22:48 UTCEG score recompute
  7. 2026-09-01 13:54 UTCEPSS rescore
  8. 2026-08-31 21:21 UTCEG score recompute
  9. 2026-08-31 20:55 UTCEG score recompute
  10. 2026-08-31 20:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71415?
CVE-2026-71415 is a high vulnerability published on August 31, 2026. Kirby is an open-source content management system. From 5.0.0 until 5.5.2, Kirby's REST API chunk upload handler in src/Api/Upload.php did not run the relevant upload authorization preflight in Kirby\Api\Upload::process() before Kirby\Api\Upload::processChunk() persisted chunk data. An…
When was CVE-2026-71415 disclosed?
CVE-2026-71415 was first published in the National Vulnerability Database on August 31, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71415 actively exploited?
CVE-2026-71415 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-71415?
CVE-2026-71415 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-71415?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71415, 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-71415

Explore →

Is Your Infrastructure Affected by CVE-2026-71415?

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

Start Free Scan →Browse All CVEs