Quick answers
- Is CVE-2026-34228 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34228 being exploited in the wild.
- How severe is CVE-2026-34228?
- Medium severity, with a CVSS score of 6.5, published 3 April 2026.
- Which products and versions are affected?
- Emlog < 2.6.8.
- Is there a fix for CVE-2026-34228?
- A patch was published on 2026-04-03: Fix committed in version 2.6.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34228 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-34228?
- Check whether you run Emlog at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in 'admin/upgrade.php' because the upgrade interface accepts remote SQL and ZIP URLs via GET parameters without validating a CSRF token. When an authenticated administrator is induced to visit a malicious URL, the server fetches and executes the remote SQL file and extracts the ZIP file directly into the web root directory. This allows for arbitrary SQL execution and arbitrary file writes (RCE). The issue was addressed in version 2.6.8 by switching the upgrade request method to POST, implementing host validation, and requiring CSRF tokens.
Affected products
- emlog emlog < 2.6.8
Timeline
- 2026-03-27: advisory: Vendor advisory published via GitHub
- 2026-04-03: disclosed: CVE published
- 2026-04-03: patched: Fix committed in version 2.6.8