CVE-2026-12815
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability has been found in coollabsio coolify 4.0.0. Impacted is an unknown function of the component Image Name Handler. Such manipulation leads to os command injection. The attack may be performed from remote. The vendor was contacted early about this disclosure but did not respond in any way. The changelog for 4.1.2 mentions "[i]mproved image, branch, proxy, and deployment input validation".
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOS command injection vulnerability in the Image Name Handler component of Coolify 4.0.0 allows remote attackers to execute arbitrary operating system commands due to insufficient input validation on image name parameters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate Coolify installationIdentify where Coolify is installed on your system (common locations include /opt/coolify, /home/coolify, or via Docker containers). Check running processes or services named 'coolify'.Affected if Coolify is not installed on the system.
-
Determine installed Coolify versionRun 'coolify --version' from the installation directory, check the Docker container image tag, or inspect the version file in the Coolify installation path (typically found in the root installation folder as version.txt or in the admin UI dashboard).Affected if The installed version falls within the affected range (4.0.0 through versions prior to 4.1.2) and has not been patched.
-
Verify Image Name Handler component is in useCheck if any project, resource, or deployment configuration within Coolify uses custom image names or pulls images from registries. Access the Coolify web UI and review projects, resources, or deployment settings that involve container image specifications.Affected if Image Name Handler is actively used for pulling or deploying container images.
-
Confirm external network exposureDetermine if the Coolify instance is accessible from untrusted networks. Check firewall rules, reverse proxy configuration, and network ACLs that expose the Coolify web interface or API ports (typically ports 80, 443, or custom ports).Affected if Coolify is reachable from external or untrusted networks without proper authentication barriers.
You are affected if Coolify version 4.0.0 is running, the Image Name Handler feature is being used to pull or deploy container images, and the instance is network-accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Coolify to version 4.1.2 or later which implements improved input validation for image, branch, proxy, and deployment parameters.
4.1.2 or later
- Upgrade Coolify to version 4.1.2 or later, as the changelog for 4.1.2 specifically mentions '[i]mproved image, branch, proxy, and deployment input validation' which addresses the command injection in the Image Name Handler component
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12815 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12815 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data