CVE-2026-26053
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 · uneditedAn Incorrect Privilege Assignment (CWE-266) vulnerability in the Command Centre Server allows an authenticated operator with limited privileges to perform some operations that they would not normally be authorized to perform. Version of Command Centre affected: 9.50 prior to vEL9.50.1587(MR1), 9.40 prior to vEL9.40.3130(MR3), 9.30 prior to vEL9.30.3983(MR5), 9.20 prior to vEL9.20.4349(MR7), all versions of 9.10.
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 · moderate confidenceThis is an Incorrect Privilege Assignment (CWE-266) vulnerability in Gallagher Command Centre Server where an authenticated operator with limited privileges can perform operations outside their authorized scope. The issue stems from improper enforcement of role-based access controls, allowing privilege escalation for certain functions within the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 9.20.4349>= 9.30.1594, < 9.30.3983>= 9.40.1359, < 9.40.3130>= 9.50.978, < 9.50.1587CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
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 if Gallagher Command Centre Server is installedCheck for the Command Centre Server installation directory (commonly C:\Program Files\Gallagher\Command Centre or /opt/gallagher/command_centre), or look for the Gallagher Command Centre service in Windows Services or systemd on Linux.Affected if The server software is present on the system.
-
Determine the installed Command Centre versionOpen the Command Centre Client, navigate to the About or System Information section, or check the version information in the installation directory (such as a version.txt file or the Windows registry under HKLM\SOFTWARE\Gallagher\Command Centre).Affected if The installed version is any version prior to the patched releases: v9.50 before 1587, v9.40 before 3130, v9.30 before 3983, v9.20 before 4349, or v9.10 any version.
-
Verify operator accounts with limited privileges existIn the Command Centre Client, navigate to Administration > Operators or Users to review configured operator accounts. Check if any operators are assigned roles with restricted permissions.Affected if There are operator accounts configured with limited or restricted role assignments.
-
Confirm role-based access control is in useIn the Command Centre Client, go to Administration > Roles or Access Control to inspect the defined roles and their assigned permissions. Verify that role-based access controls are enabled in the system configuration.Affected if Role-based access control is configured and enforced for operator accounts.
A user is affected if they have Gallagher Command Centre Server installed with a version prior to the patched releases AND have operator accounts configured with limited privileges using role-based access controls.
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 · scoped9.20.43499.30.39839.40.3130
Upgrade Command Centre Server to the patched versions: vEL9.50.1587(MR1), vEL9.40.3130(MR3), vEL9.30.3983(MR5), vEL9.20.4349(MR7) or later. For version 9.10, contact vendor for patch availability.
Upgrade to the minimum fixed version for your current branch: vEL9.50.1587(MR1) for 9.50, vEL9.40.3130(MR3) for 9.40, vEL9.30.3983(MR5) for 9.30, vEL9.20.4349(MR7) for 9.20, or migrate from 9.10 to a supported version
- 1. Identify the current version of Gallagher Command Centre Server by accessing the Command Centre administration interface or checking system documentation
- 2. Determine which version branch you are currently on (9.10, 9.20, 9.30, 9.40, or 9.50)
- 3. For Command Centre 9.50: upgrade to version vEL9.50.1587 (MR1) or later
- 4. For Command Centre 9.40: upgrade to version vEL9.40.3130 (MR3) or later
- 5. For Command Centre 9.30: upgrade to version vEL9.30.3983 (MR5) or later
- 6. For Command Centre 9.20: upgrade to version vEL9.20.4349 (MR7) or later
- 7. For Command Centre 9.10: upgrade to a supported version (9.20 or higher) that includes the security fix
- 8. Test the upgrade in a non-production environment before deploying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26053 — 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-26053 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