CVE-2026-26009
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 · uneditedCatalyst is a platform built for enterprise game server hosts, game communities, and billing panel integrations. Install scripts defined in server templates execute directly on the host operating system as root via bash -c, with no sandboxing or containerization. Any user with template.create or template.update permission can define arbitrary shell commands that achieve full root-level remote code execution on every node machine in the cluster. This vulnerability is fixed in commit 11980aaf3f46315b02777f325ba02c56b110165d.
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 confidenceCatalyst platform allows users with template.create or template.update permissions to define install scripts that execute directly as root via bash -c on all cluster nodes without any sandboxing or containerization, enabling full remote code execution at root level across the entire infrastructure.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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.
-
Check if you have template management permissionsReview your user role and permissions in the Catalyst platform admin console or query the permissions API for template.create or template.update privileges assigned to your account or roleAffected if Your user account or role has template.create or template.update permissions enabled
-
Verify the template feature is accessibleLog into the Catalyst platform and navigate to the template management section, or query the API endpoint for template creation and editing capabilitiesAffected if The template creation or update functionality is available and functional in your environment
-
Determine your Catalyst platform versionRun 'catalyst --version' or check the platform version through the admin dashboard, or inspect the installed package version via your package managerAffected if The installed version has not received the security fix from commit 11980aaf3f46315b02777f325ba02c56b110165d (compare against any published patched versions)
-
Confirm install script execution contextCreate a test template with an install script and inspect the execution configuration, or review the template execution logs to verify scripts run via 'bash -c' as root without sandboxing or containerizationAffected if Templates execute install scripts directly as root using bash -c without any sandbox or container isolation
You are affected if you have users with template.create or template.update permissions in a Catalyst platform version where template install scripts execute as root via bash -c without sandboxing.
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.
From vendor dataImmediately restrict template.create and template.update permissions to only highly trusted administrators, and implement the fix from commit 11980aaf3f46315b02777f325ba02c56b110165d which adds proper sandboxing or containerization for template script execution.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26009 — 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-26009 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