How many CVEs have patched forceDelete?

1 published CVEs changed forceDelete in coollabsio/coolify, in 2 distinct patches totalling 6 changed lines, between 2026 and 2026.

What is the latest CVE that changed forceDelete?

CVE-2026-34037 (Cross-Tenant Resource Cloning via Broken Object-Level Authorization in cloneTo()), published 2026-07-07, changed lines 64 of app/Policies/StandaloneDockerPolicy.php.

How does forceDelete compare to the rest of coollabsio/coolify?

coollabsio/coolify has 43 CVEs with a located fix in total; 1 of them changed forceDelete.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

coollabsio/coolify

Function

2 files

forceDelete

Name: forceDelete in coollabsio/coolify: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

Defined in 2 files

Last patched July 7, 2026

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

6

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

forceDelete in coollabsio/coolify was changed by 1 published CVE fixes in 2026, in 2 distinct patches that added or removed 6 lines in total.

The name occurs in 2 files: app/Policies/StandaloneDockerPolicy.php, app/Policies/SwarmDockerPolicy.php.

coollabsio/coolify has 43 CVEs with a located fix in total, so 2% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed forceDelete, newest first, with the lines each fix touched.

Cross-Tenant Resource Cloning via Broken Object-Level Authorization in cloneTo()
CVE-2026-34037 · app/Policies/StandaloneDockerPolicy.php · line 64 · +1 −2
Critical · CVSS 9.9
EPSS 0.4%2026-07-07
Cross-Tenant Resource Cloning via Broken Object-Level Authorization in cloneTo()
CVE-2026-34037 · app/Policies/SwarmDockerPolicy.php · line 64 · +1 −2
Critical · CVSS 9.9
EPSS 0.4%2026-07-07

Get an alert when the next CVE fix lands in coollabsio/coolify, with the patched functions.

Monitor coolify CVEs

Other functions in these files

Functions in the same files that CVE fixes also changed.

Other hotspots in the repository

Functions in coollabsio/coolify changed by the most CVE fixes.

backup_standalone_mongodb7 CVEs · app/Jobs/DatabaseBackupJob.php syncData7 CVEs · app/Livewire/Project/Database/BackupEdit.php save_new_init_script6 CVEs · app/Livewire/Project/Database/Postgresql/General.php delete_init_script6 CVEs · app/Livewire/Project/Database/Postgresql/General.php save_init_script6 CVEs · app/Livewire/Project/Database/Postgresql/General.php submitFileStorageDirectory6 CVEs · app/Livewire/Project/Service/Storage.php

All patched functions in coollabsio/coolify

Frequently asked questions

Common questions about CVE fixes to forceDelete.

How many CVEs have patched forceDelete?: 1 published CVEs changed forceDelete in coollabsio/coolify, in 2 distinct patches totalling 6 changed lines, between 2026 and 2026.
What is the latest CVE that changed forceDelete?: CVE-2026-34037 (Cross-Tenant Resource Cloning via Broken Object-Level Authorization in cloneTo()), published 2026-07-07, changed lines 64 of app/Policies/StandaloneDockerPolicy.php.
How does forceDelete compare to the rest of coollabsio/coolify?: coollabsio/coolify has 43 CVEs with a located fix in total; 1 of them changed forceDelete.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track coollabsio/coolify CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing