dbcve.org
Firewall CommunityApplication · Endian

CVE-2026-34792

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_clamav.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 in Endian Firewall's /cgi-bin/logs_clamav.cgi where the DATE parameter is passed to a Perl open() call without proper regex validation, allowing arbitrary OS command execution.

MitigationRestrict access to the affected CGI script, implement proper input validation/sanitization on the DATE parameter to prevent command injection, and audit similar CGI scripts for comparable vulnerabilities.

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. Confirm Endian Firewall installation
    Check if the system is running Endian Firewall by examining /etc/redhat-release, /etc/issue, or running 'Endian' related system commands. The web interface typically runs on port 10443 or 443.
    Affected if The system is not an Endian Firewall Community edition
  2. Identify installed Endian Firewall version
    Check the installed version via the web UI (typically displayed on the dashboard or in System > Status), or via command line by examining RPM package: rpm -q endian-firewall or checking /var/log/endian/version
    Affected if The installed version is 3.3.25 or prior
  3. Verify vulnerable CGI script exists
    Check if the file /cgi-bin/logs_clamav.cgi exists on the web server. This is typically located in the /var/www/cgi-bin/ directory or equivalent web root.
    Affected if The logs_clamav.cgi script does not exist on the system
  4. Confirm web interface is accessible
    Verify the Endian Firewall web interface is running and accessible on the expected ports (10443 or 443). Check with: netstat -tlnp | grep -E '10443|443' or test HTTP/HTTPS connectivity to the interface.
    Affected if The web interface is not running or not accessible from your network perspective
  5. Check authentication status for CGI endpoint
    Determine if authentication is required to access the logs_clamav.cgi endpoint. This typically uses the Endian Firewall's internal authentication system. Review web server configuration files in /etc/httpd/ or equivalent for access controls.
    Affected if The CGI endpoint is accessible without authentication (unauthenticated exploitation path exists)

The environment is affected if it is an Endian Firewall Community version 3.3.25 or prior, the logs_clamav.cgi script is present, the web interface is accessible, and the DATE parameter can be manipulated through the CGI endpoint.

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

Restrict access to the affected CGI script, implement proper input validation/sanitization on the DATE parameter to prevent command injection, and audit similar CGI scripts for comparable vulnerabilities.

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