dbcve.org
BluvoyixApplication · Blusparkglobal

CVE-2026-22236

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The vulnerability exists in BLUVOYIX due to improper authentication in the BLUVOYIX backend APIs. An unauthenticated remote attacker could exploit this vulnerability by sending specially crafted HTTP requests to the vulnerable APIs. Successful exploitation of this vulnerability could allow the attacker to gain full access to customers' data and completely compromise the targeted platform.

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 confidence

BLUVOYIX contains an improper authentication vulnerability in its backend APIs. An unauthenticated remote attacker can send specially crafted HTTP requests to bypass authentication controls and gain full access to customer data, completely compromising the platform.

MitigationImplement proper authentication and authorization mechanisms across all backend APIs, including robust session management, token validation, and access controls. Conduct thorough security testing to verify authentication bypass is no longer possible.

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
BluvoyixApplication
Affected:all versions

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Bluvoyix installation and version
    Locate the Bluvoyix installation directory and check for version information in product metadata, about pages, or version files. If using a managed service, query your inventory or deployment records for the installed Bluvoyix version.
    Affected if Any version of Bluvoyix is confirmed to be installed, as all versions are affected by this vulnerability.
  2. Identify exposed backend API endpoints
    Review network configuration, firewall rules, reverse proxy configurations, or API gateway settings to determine which Bluvoyix backend API endpoints are network-accessible. Check for exposed HTTP/HTTPS ports or paths that serve API functionality.
    Affected if Backend API endpoints are externally or broadly accessible beyond intended trusted networks.
  3. Verify API authentication configuration
    Examine the Bluvoyix configuration files, typically found in config directories or deployment manifests, that define authentication settings for API endpoints. Look for settings controlling anonymous access, token validation, session management, or authentication bypass flags.
    Affected if Configuration permits unauthenticated or improperly authenticated access to sensitive API endpoints, or authentication enforcement is missing for any API route.
  4. Inspect access logs for anomalous API requests
    Review Bluvoyix server access logs, authentication logs, or security audit logs for patterns indicating unauthenticated API access, such as successful requests without valid authentication tokens, unusual API call sources, or access to customer data endpoints from unknown sessions.
    Affected if Logs show API requests accessing sensitive data or administrative functions without valid authentication credentials.
  5. Test API authentication enforcement
    Send a crafted HTTP request to a protected Bluvoyix API endpoint (such as an endpoint that should require authentication for customer data) without including authentication credentials or with malformed credentials, and observe whether the request is accepted or rejected.
    Affected if The API accepts the request and returns customer data or privileged functionality without requiring valid authentication.

If Bluvoyix is installed and its backend APIs are network-accessible, the environment is likely affected unless explicit authentication enforcement is confirmed to be in place and functioning correctly.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and authorization mechanisms across all backend APIs, including robust session management, token validation, and access controls. Conduct thorough security testing to verify authentication bypass is no longer possible.

Fix this in Bluvoyix Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22236 — 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-22236 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