dbcve.org
Firewall CommunityApplication · Endian

CVE-2026-34797

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_smtp.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 · high confidence

Endian Firewall 3.3.25 and prior contains a command injection vulnerability in the /cgi-bin/logs_smtp.cgi web script. The DATE parameter is not properly validated before being used in a Perl open() call to construct a file path, allowing authenticated users to inject and execute arbitrary OS commands.

MitigationImplement strict input validation on the DATE parameter using whitelist approaches or sanitize shell metacharacters, and replace the unsafe Perl open() call with safer alternatives such as taint mode or explicit file handle operations.

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 the system is running Endian Firewall by looking for its characteristic web interface, or check the installed packages/version using the system package manager if SSH access is available
    Affected if The system is running Endian Firewall Community edition
  2. Determine Endian Firewall version
    Access the web administration interface and check the version displayed in the footer or system information page, or run 'rpm -q endian-firewall' or 'cat /etc/redhat-release' if SSH access is available
    Affected if The installed version is 3.3.25 or any version prior to 3.3.25
  3. Verify logs_smtp.cgi exists
    Check if the CGI script exists at /cgi-bin/logs_smtp.cgi on the web server by attempting to access it via HTTP/HTTPS request, or listing the cgi-bin directory if filesystem access is available
    Affected if The file /cgi-bin/logs_smtp.cgi exists on the system
  4. Confirm authentication status
    Verify that the web interface requires authentication for access, and check if valid session credentials can be obtained for the logs_smtp.cgi endpoint
    Affected if Authenticated access to the logs_smtp.cgi endpoint is possible (authentication can be bypassed or valid credentials exist)
  5. Check DATE parameter usage
    Inspect the logs_smtp.cgi script source code if accessible, or observe the behavior of the DATE parameter when making requests to the CGI endpoint with various input values
    Affected if The DATE parameter is used directly in file path operations without sanitization

The environment is affected if it runs Endian Firewall Community version 3.3.25 or prior, has the logs_smtp.cgi script accessible, and the DATE parameter is used unsanitized in the Perl open() call.

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.

From vendor data
Upgrade available Upgrade to a release after 3.3.25
Interim mitigation

Implement strict input validation on the DATE parameter using whitelist approaches or sanitize shell metacharacters, and replace the unsafe Perl open() call with safer alternatives such as taint mode or explicit file handle operations.

Fix this in Firewall Community Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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