CVE-2026-34965
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 · uneditedCockpit CMS contains an authenticated remote code execution vulnerability in the /cockpit/collections/save_collection endpoint that allows authenticated attackers with collection management privileges to inject arbitrary PHP code into collection rules parameters. Attackers can inject malicious PHP code through rule parameters which is written directly to server-side PHP files and executed via include() to achieve arbitrary command execution on the underlying server.
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 confidenceCockpit CMS has an authenticated RCE vulnerability in the /cockpit/collections/save_collection endpoint. Attackers with collection management privileges can inject malicious PHP code into collection 'rules parameters', which are written directly to server-side PHP files and executed via include(), achieving arbitrary command execution.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Identify Cockpit CMS installation and versionCheck for cockpit directory in web root, review version.php or composer.json file for installed version numberAffected if Cockpit CMS is present and version has not received the security patch for this vulnerability
-
Verify collections module is enabledCheck config or settings for 'collections' module status; look for /cockpit/collections/ routes in the applicationAffected if Collections module is active and accessible via the API
-
Confirm save_collection endpoint existsInspect application routing or attempt aHEAD request to /cockpit/collections/save_collection (requires authentication context)Affected if The endpoint is reachable and accepts POST requests with collection rule parameters
-
Inspect collection storage PHP filesLocate storage directory for collections (typically storage/collections/ or similar); examine PHP files for raw PHP code tags that may have been injected into rule parametersAffected if PHP files in collection storage contain suspicious eval(), shell_exec(), system() or similar function calls that were not authored by developers
-
Check authentication enforcement on vulnerable endpointReview authentication middleware on /cockpit/collections/ routes; determine if collection management privileges are required for save_collectionAffected if The endpoint permits access to users with collection management permissions without additional sanitization of rule parameters
User is affected if running an unpatched Cockpit CMS with the collections module enabled where the save_collection endpoint accepts authenticated requests with collection management privileges and writes rule parameters to executable PHP files.
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 dataImplement strict input validation on rules parameters to prevent PHP code injection, and refactor the storage mechanism to avoid writing user-controlled data to PHP files that get included—use safe serialization or database storage instead.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.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 $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34965 — 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-34965 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