CVE-2026-25193
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 · uneditedInsertion of Sensitive Information into Log File (CWE-532) in some Command Centre Service installers could lead to Service Account credentials exposure. Mitigating Factor: Only sites that install Command Centre Services with a custom Service Account (not the default Network Service account) are potentially impacted. Mitigation: For sites concerned about exposure, the recommended action is to change the Service Account password. They can also delete any installer log files, usually found in %programdata%\Gallagher\Command Centre.
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 confidenceThe Command Centre Service installers write Service Account credentials to log files during installation (CWE-532). When sites use a custom Service Account instead of the default Network Service, these credentials are stored in plaintext log files typically located in %programdata%\Gallagher\Command Centre, potentially exposing them to unauthorized users.
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.10.05< 9.30.104< 9.40.2575< 2.0.9< 10.0.8< 9.60.10< 1.0.10< 2.0.5CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Confirm Command Centre installationCheck if the directory %programdata%\Gallagher\Command Centre exists on the systemAffected if Directory does not exist means Command Centre is not installed and not affected by this CVE
-
Identify the configured Service AccountOpen Services console (services.msc), locate the Gallagher Command Centre service, right-click and select Properties, then note the account name in the 'Log on as' fieldAffected if A custom domain or local user account is configured (not 'NT AUTHORITY\Network Service' or 'LocalSystem') means credentials could have been written to logs
-
Locate installer log filesBrowse to %programdata%\Gallagher\Command Centre and look for any log files (typically with .log extension) that may have been created during installationAffected if Log files exist from the initial installation or reinstallation means potential exposure
-
Search log files for credentialsOpen each log file found and search for strings resembling passwords, or look for the Service Account username appearing near password-related keywords or in plain textAffected if Log files contain the Service Account username and password in plain text (not masked or hashed) means the system is vulnerable and credentials are exposed
The system is affected if Command Centre is installed with a custom Service Account and installer log files in %programdata%\Gallagher\Command Centre contain plain text credentials for that service account.
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 data1.0.102.0.52.0.9
Change the Service Account password immediately to prevent ongoing credential exposure, and delete all installer log files from %programdata%\Gallagher\Command Centre to remove the sensitive information.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25193 — 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-25193 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