CVE-2026-14453
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 · uneditedThis vulnerability is a critical Server-Side Template Injection (SSTI) in Centreon's centreon-open-tickets module that leads to Remote Code Execution. The message_confirm field is stored without sanitization and rendered via Smarty with no security policy enabled, allowing any authenticated user, to inject and execute arbitrary code on the server. This results in disclosure of environment secrets and could impact platform availability of Centreon Infra Monitoring product.
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 confidenceA critical Server-Side Template Injection (SSTI) vulnerability exists in Centreon's centreon-open-tickets module where the message_confirm field is stored without sanitization and rendered through the Smarty templating engine without security policies enabled. This allows any authenticated user to inject arbitrary Smarty template code that executes on the server, leading to full remote code execution, exposure of environment secrets, and potential denial of service.
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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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.
-
Verify centreon-open-tickets module is installedCheck for the presence of the centreon-open-tickets module in Centreon's web interface under Administration > Extensions > Modules, or list installed Centreon modules via CLI: ls -la /usr/local/centreon/www/modules/ or rpm -qa | grep centreon-open-ticketsAffected if The centreon-open-tickets module is installed and no patch has been applied to sanitize the message_confirm field
-
Identify the installed centreon-open-tickets versionView the module version in Centreon's web interface (Administration > Extensions > Modules > centreon-open-tickets) or check the module's conf.php or module.xml file for the version number, then compare against any patched versions released by CentreonAffected if The installed version has not been patched to validate or encode the message_confirm field before storage or rendering
-
Confirm Smarty security policy is disabledLocate the Smarty configuration file used by centreon-open-tickets (typically in /usr/local/centreon/www/modules/centreon-open-tickets/ or within the Smarty template rendering code) and check for the presence of $smarty->enableSecurity() or $smarty->disableSecurity() calls; if disableSecurity() is called or no security policy is set, the vulnerability is exploitableAffected if Smarty security policy is not enabled, allowing arbitrary Smarty template execution in the message_confirm field
-
Inspect the message_confirm field configurationNavigate to the open tickets provider configuration in Centreon's web interface (Configuration > Notifications > OpenTickets > or similar path depending on version) and examine the message_confirm field definition; check the database table storing provider configurations (such as open_tickets_xxx tables) for the message_confirm field to see if raw Smarty syntax is stored without escapingAffected if The message_confirm field accepts and stores raw template syntax that gets rendered by Smarty without sanitization
-
Review access controls on open tickets configurationCheck Centreon's user access rights (Administration > Users > Access management > ACL) to determine which authenticated users have permission to create or modify open ticket provider configurations containing the message_confirm field; any user with write access to these configurations can trigger the SSTIAffected if Authenticated users with limited privileges can still modify open ticket provider settings containing the vulnerable message_confirm field
Your environment is affected if centreon-open-tickets is installed and the message_confirm field is rendered through Smarty without input sanitization and with Smarty security policies disabled.
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 and output encoding for the message_confirm field before storage, and enable Smarty's security policy with disabled PHP functions and restricted tags to prevent template injection. Alternatively, upgrade centreon-open-tickets to a patched version if available.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14453 — 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-14453 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