dbcve.org
Firewall CommunityApplication · Endian

CVE-2026-34794

HIGH · 8.8 CVSS v3.1 Published 2026-04-02
Fix available
A fix is available. Upgrade to after 3.3.25 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Endian Firewall version 3.3.25 and prior allow authenticated users to execute arbitrary OS commands via the DATE parameter to /cgi-bin/logs_ids.cgi. The DATE parameter value is used to construct a file path that is passed to a Perl open() call, which allows command injection due to an incomplete regular expression validation.

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

Endian Firewall 3.3.25 and prior contains an OS command injection vulnerability in the /cgi-bin/logs_ids.cgi CGI script. The DATE parameter is used to construct a file path passed to a Perl open() call without proper sanitization, allowing authenticated users to inject arbitrary OS commands through incomplete regex validation.

MitigationUpdate to a patched version of Endian Firewall if available. If no patch exists, restrict access to /cgi-bin/logs_ids.cgi to only necessary authenticated users and implement strict input validation on the DATE parameter to prevent shell metacharacter injection.

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
Firewall CommunityApplication
Affected:<= 3.3.25

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 checks

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

  1. Identify Endian Firewall installation
    Check if Endian Firewall is installed on the system by looking for the product in your package manager, or by identifying the system hostname and network configuration typical of Endian Firewall appliances.
    Affected if Endian Firewall Community edition is installed on the system.
  2. Determine installed version
    Check the installed version of Endian Firewall Community. This can typically be found in the system information page of the web interface, or by running system commands like 'cat /etc/redhat-release' or checking the endian-version file if present.
    Affected if The installed version is 3.3.25 or any prior version (3.3.x <= 3.3.25).
  3. Verify vulnerable CGI script exists
    Check if the file /cgi-bin/logs_ids.cgi exists on the web server. This file is part of the web interface and should be present in versions 3.3.x.
    Affected if The logs_ids.cgi file exists in the/cgi-bin/ directory of the web interface.
  4. Assess web interface accessibility
    Determine if the Endian Firewall web interface is accessible from untrusted networks. Check firewall rules, NAT configurations, or reverse proxy settings that may expose the web interface to the internet or untrusted internal segments.
    Affected if The web interface (typically ports 443 or 8443) is accessible from networks outside your trusted user base.
  5. Check for existing authentication
    Verify whether the web interface authentication can be bypassed or if default credentials are in use. Review any exposed login pages for the logs_ids.cgi functionality.
    Affected if Untrusted or unknown users can authenticate to the Endian Firewall web interface.

You are affected if Endian Firewall Community version 3.3.25 or prior is installed, the logs_ids.cgi script is present, and the web interface is accessible to untrusted users who could exploit the DATE parameter command injection.

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 a release after 3.3.25
Interim mitigation

Update to a patched version of Endian Firewall if available. If no patch exists, restrict access to /cgi-bin/logs_ids.cgi to only necessary authenticated users and implement strict input validation on the DATE parameter to prevent shell metacharacter injection.

Recommended fix Moderate confidence

Endian Firewall Community version > 3.3.25 (latest stable release)

  1. 1. Back up the current Endian Firewall configuration before making any changes.
  2. 2. Verify the current installed version via the web interface (Dashboard > System Information) or via CLI: cat /etc/redhat-release
  3. 3. Download the latest Endian Firewall Community release from the official Endian repository or ISO images.
  4. 4. Upgrade the firewall following the official upgrade documentation: https://help.endian.com/hc/en-us/articles/360042368514-Upgrade
  5. 5. After upgrade, verify the new version is greater than 3.3.25.
  6. 6. Test the /cgi-bin/logs_ids.cgi functionality to ensure it still works properly with valid inputs.
  7. 7. Review user access controls to ensure only necessary users have access to the web interface.
Caveat Review release notes for any configuration syntax changes between your current version and the target upgrade version before applying.

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

Fix this in Firewall Community Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34794 — 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-34794 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