dbcve.org
Pandora FmsApplication · Artica

CVE-2026-34188

HIGH · 7.2 CVSS v3.1 Published 2026-04-13
Fix available
A fix is available. Upgrade to 800.1 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Improper Neutralization of Special Elements used in an OS Command vulnerability allows OS Command Injection via Event Response execution. This issue affects Pandora FMS: from 777 through 800

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 confidence

This is an OS Command Injection vulnerability in Pandora FMS affecting versions 777 through 800. The vulnerability exists in the Event Response functionality where improper neutralization of special elements allows attackers to inject arbitrary OS commands. With a CVSS score of 7.2, this high-severity issue could allow authenticated attackers to execute commands on the underlying operating system.

MitigationApply vendor patches for Pandora FMS version 800 or later. If patches are unavailable, implement input validation and avoid direct shell command execution in Event Response functionality. Additionally, restrict access to the Event Response feature to minimize attack surface.

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
Pandora FmsApplication
Affected:>= 777, < 800.1

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Pandora FMS installation
    Locate the Pandora FMS installation directory or check for running pandora processes (e.g., ps aux | grep pandora, or look for /var/www/html/pandora, /opt/pandora, etc.)
    Affected if Pandora FMS is found on the system
  2. Determine installed Pandora FMS version
    Check the version file or admin interface. Common locations: include/config.php (look for $config['version'] or similar), or login to the web UI and check About/System Info page
    Affected if Installed version is 777 through 799.x (anything >=777 and <800.1)
  3. Verify Event Response module is accessible
    Check if Event Response feature exists: look for 'responses' or 'event responses' in the Pandora FMS web UI (typically under Events menu), or check for the responses table in the Pandora database
    Affected if Event Response functionality is present and accessible
  4. Check for custom event responses using shell commands
    Examine the database table PandoraFMS uses for event responses (often named tentacle, tengine, or similar in the Pandora database), or check /opt/pandora/pandora_console/attachment/responses/ directory for custom scripts
    Affected if Custom event responses exist that execute shell commands (especially if they accept user input as parameters)
  5. Confirm authentication access to Event Response feature
    Review user/role permissions in Pandora FMS admin panel under Users or ACLs to see which users can access or create Event Responses
    Affected if Multiple users or users with lower privilege levels have access to create/edit Event Responses

A system is affected if it runs Pandora FMS version 777-799.x with the Event Response feature enabled and accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 800.1 or later
Fixed in 800.1
Interim mitigation

Apply vendor patches for Pandora FMS version 800 or later. If patches are unavailable, implement input validation and avoid direct shell command execution in Event Response functionality. Additionally, restrict access to the Event Response feature to minimize attack surface.

Recommended fix High confidence

800.1

  1. Review the official Pandora FMS upgrade documentation at pandorafms.com for your current installation method
  2. Ensure you have a complete backup of your Pandora FMS database and configuration files
  3. Stop the Pandora FMS services before upgrading
  4. Upgrade Pandora FMS to version 800.1 or later
  5. Verify the upgrade was successful by checking the version number in the web interface
  6. Restart Pandora FMS services
  7. Test that Event Response functionality works correctly after the upgrade
  8. Monitor system logs for any unusual activity
Caveat Review release notes for 800.1 for any configuration or feature changes that may require adjustments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pandora Fms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34188 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34188 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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