CVE-2026-45567
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. In versions 8.2.6.4 and prior, there is an authentication bypass vulnerability via 'api' substring in URL + unauthenticated /api/gpt. At time of publication, there are no publicly available patches.
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 · moderate confidenceRoxy-WI versions 8.2.6.4 and prior contain an authentication bypass vulnerability where certain API endpoints containing the 'api' substring (specifically /api/gpt) can be accessed without authentication. This allows unauthenticated attackers to potentially access sensitive management functionality of the web interface used for Haproxy, Nginx, Apache, and Keepalived server administration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
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 installationCheck for Roxy-WI by looking for its web interface, typically running on ports 80/443, or check for installation directories like /opt/roxy-wi, /usr/share/roxy-wi, or the configuration file roxy-wi.confAffected if Roxy-WI is installed on the system
-
Determine installed Roxy-WI versionCheck the version file or banner - typically found in the installation directory, or query the web interface login page for version information in the HTML source or response headersAffected if The installed version is 8.2.6.4 or any prior version (anything <= 8.2.6.4)
-
Verify unauthenticated API access vulnerabilitySend an HTTP GET request to /api/gpt without providing any authentication credentials (no session cookie, no Authorization header)Affected if The endpoint returns a successful HTTP response (200 OK) instead of redirecting to login or returning 401/403
-
Inspect access logs for unauthorized API accessReview Roxy-WI access logs (typically in /var/log/roxy-wi/ or the web server logs) for GET requests to /api/gpt or any endpoint containing '/api/' from IP addresses that did not authenticate firstAffected if There are log entries showing requests to /api/gpt or similar API endpoints without prior authentication events for those source IPs
-
Check network exposure of Roxy-WI interfaceVerify which network interfaces and IP addresses the Roxy-WI web service is bound to, and check firewall rules or cloud security groups to determine if the web interface is accessible from untrusted networksAffected if Roxy-WI is bound to a public IP or accessible from networks outside the trusted administrative zone
A system is affected if Roxy-WI version 8.2.6.4 or lower is installed and the /api/gpt endpoint responds without authentication, or if logs show unauthenticated access attempts to API endpoints.
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 dataSince no patch is available, restrict network access to the Roxy-WI interface using firewall rules or network segmentation to limit exposure to trusted sources only. Monitor access logs for any requests to /api/gpt or similar API endpoints from unauthorized IP addresses.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45567 — 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-45567 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