CVE-2026-34796
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 · uneditedEndian Firewall version 3.3.25 and prior allow authenticated users to execute arbitrary OS commands via the DATE parameter to /cgi-bin/logs_openvpn.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 confidenceEndian Firewall 3.3.25 and prior contains a command injection vulnerability in /cgi-bin/logs_openvpn.cgi. The DATE parameter is used to construct a file path passed to Perl's open() function without proper sanitization, allowing authenticated users to execute arbitrary OS commands through incomplete regex validation.
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<= 3.3.25CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Endian Firewall installationCheck if the system is running Endian Firewall by looking for the product banner on the web interface (typically port 10443) or checking for /var/log/efw directory structure.Affected if The system is running Endian Firewall Community edition.
-
Determine installed versionCheck the installed version by viewing /etc/e-smith-release or the web interface login page footer. Alternatively, run: cat /etc/e-smith-releaseAffected if The version is 3.3.25 or lower.
-
Verify vulnerable CGI script existsCheck if the file /cgi-bin/logs_openvpn.cgi exists on the web server. This can be done via: ls -la /httpd/cgi-bin/logs_openvpn.cgi or curl -k https://<host>:10443/cgi-bin/logs_openvpn.cgiAffected if The CGI script file exists and responds to requests.
-
Check if web interface is accessibleVerify the Endian web interface is reachable on port 10443 (HTTPS) or port 80 (HTTP). Test with: curl -k -I https://<host>:10443/Affected if The administrative web interface is exposed and accessible.
-
Confirm authentication is enabledVerify that the web interface requires authentication. The vulnerability requires a valid authenticated session to exploit the DATE parameter.Affected if The web interface accepts authentication credentials.
You are affected if you are running Endian Firewall Community version 3.3.25 or prior with the web interface accessible and the vulnerable CGI script present, as an authenticated attacker could inject commands via the DATE parameter.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict input validation on the DATE parameter using a whitelist approach and replace Perl open() calls with safer alternatives such as open() with separate arguments or sysopen(). Apply the vendor patch when available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-34796 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34796 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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