CVE-2026-33076
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 · uneditedRoxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers. Prior to version 8.2.6.4, the haproxy_section_save interface presents a vulnerability that could lead to remote code execution due to path traversal and writing into scheduled tasks. Version 8.2.6.4 fixes the issue.
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 confidenceRoxy-WI versions prior to 8.2.6.4 contain a path traversal vulnerability in the haproxy_section_save interface that allows attackers to write arbitrary files to the filesystem, including scheduled task files (e.g., cron jobs), leading to remote code execution with the privileges of the web server process.
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< 8.2.6.4CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 Roxy-WI installationLocate Roxy-WI by checking common installation directories (e.g., /opt/roxy-wi, /usr/local/roxy-wi) or by querying running processes for roxy-wi, haproxy-wi, or the web server serving it.Affected if Roxy-WI is found running on the system
-
Determine installed Roxy-WI versionCheck the version file typically found in the Roxy-WI installation directory, or access the web interface and look for a version indicator in the UI (usually in About or Settings). Compare the version number to 8.2.6.4.Affected if The installed version is lower than 8.2.6.4 (e.g., 8.2.6.3, 8.2.5.0, etc.)
-
Verify haproxy_section_save interface accessibilityCheck if the web management interface is exposed to network access. This endpoint is typically at /<roxy-wi-path>/haproxy_section_save or similar. Inspect web server configuration for Roxy-WI to determine if this route is enabled.Affected if The Roxy-WI web interface is accessible and the haproxy_section_save functionality is enabled
-
Inspect scheduled tasks for unauthorized entriesReview cron jobs (crontab -l for all users), systemd timers, and scheduled task files in /etc/cron.d/, /etc/cron.daily/, /etc/cron.hourly/ for entries that were not explicitly created by your organization.Affected if Unexpected or suspicious cron entries exist, especially those pointing to scripts in writable directories or executing commands from unknown sources
The environment is affected if Roxy-WI version is below 8.2.6.4 AND the management interface with haproxy_section_save is network-accessible AND unauthorized scheduled tasks are present on the system.
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.
dbcve · scoped8.2.6.4
Upgrade Roxy-WI to version 8.2.6.4 or later. If immediate patching is not possible, restrict network access to the Roxy-WI management interface and audit existing scheduled tasks for unauthorized entries.
8.2.6.4
- Backup the current Roxy-WI installation and configuration
- Download Roxy-WI version 8.2.6.4 from the official GitHub repository or release page
- Upgrade the Roxy-WI installation to version 8.2.6.4 using the standard upgrade procedure for your deployment method (pip, Docker, or source)
- Restart the Roxy-WI service to ensure the new version is fully active
- Verify the version has been successfully upgraded by checking the web interface or command line
- Confirm that the haproxy_section_save interface is functioning correctly and the path traversal vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33076 — 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-33076 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