dbcve.org
Firewall CommunityApplication · Endian

CVE-2026-34795

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_log.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

Authenticated command injection vulnerability in Endian Firewall's web interface (logs_log.cgi). The DATE parameter is passed unsanitized to a Perl open() call, allowing arbitrary OS command execution through incomplete regex validation.

MitigationUpdate to patched version if available; otherwise restrict access to logs_log.cgi and implement strict input validation on all parameters before use in file 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. Verify Endian Firewall Community version
    Check the installed Endian Firewall version. On the firewall console or via system queries, look for version 3.3.25 or lower. Common methods: check /etc/version, the web UI footer, or the package management system.
    Affected if Installed version is 3.3.25 or any prior version (3.3.x series)
  2. Confirm logs_log.cgi script exists
    Locate the CGI script logs_log.cgi in the web root. Typical paths include /usr/lib/cgi-bin/logs_log.cgi or within the web server document root under /cgi-bin/. Use: find / -name 'logs_log.cgi' 2>/dev/null
    Affected if The script exists at /cgi-bin/logs_log.cgi or within the web CGI directory
  3. Verify web interface is accessible
    Confirm the Endian Firewall web management interface is running and accessible. Test connectivity to the CGI endpoint: curl -k https://<your-firewall-ip>/cgi-bin/logs_log.cgi
    Affected if The web interface responds and the CGI script is reachable over HTTP/HTTPS
  4. Check if authentication is enabled
    Verify the firewall authentication system is configured. Command injection requires an authenticated session, so determine if local user accounts or remote authentication (RADIUS/LDAP) is active.
    Affected if Authentication is configured and valid user credentials exist for the web UI

You are affected if Endian Firewall Community version 3.3.25 or lower is installed and the logs_log.cgi CGI script is present and accessible, as the DATE parameter in that script can be exploited without proper input sanitization.

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 patched version if available; otherwise restrict access to logs_log.cgi and implement strict input validation on all parameters before use in file operations.

Recommended fix Moderate confidence

Latest stable Endian Firewall Community release (newer than 3.3.25)

  1. Check the current Endian Firewall Community version using the web interface or command line (grep VERSION /etc/redhat-release or similar)
  2. Backup all firewall configurations and critical data before proceeding with any upgrade
  3. Visit help.endian.com or the official Endian download page to obtain the latest stable release of Endian Firewall Community
  4. Review the release notes for the latest version to confirm the command injection vulnerability is addressed
  5. Follow the official upgrade documentation to perform a clean upgrade or migration to the latest version
  6. After upgrade, verify the /cgi-bin/logs_log.cgi endpoint no longer allows command injection through the DATE parameter
  7. Confirm authentication is still required for the affected CGI endpoint
  8. Test that legitimate log viewing functionality still works correctly
Caveat Review upgrade documentation for migration steps; Community edition may have limitations compared to paid editions; backup before upgrading

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-34795 — 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-34795 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