# CVE-2026-22239: Email Sending Vulnerability in BLUVOYIX

> Unauthenticated attackers can send unsolicited emails via the BLUVOYIX email API due to design flaws, enabling spam campaigns.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/RE:H/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jan 2026
- **Updated:** 14 Jan 2026
- **Also known as:** GHSA-v9rm-r464-44x6

## What is CVE-2026-22239?

CVE-2026-22239 is a critical vulnerability in Bluspark Global BLUVOYIX, published on 14 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The vulnerability exists in BLUVOYIX due to design flaws in the email sending API. An unauthenticated remote attacker could exploit this vulnerability by sending specially crafted HTTP requests to the vulnerable email sending API. Successful exploitation of this vulnerability could allow the attacker to send unsolicited emails to anyone on behalf of the company.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-22239?

It affects 1 product.


Products: Blusparkglobal Bluvoyix.

## How do I fix CVE-2026-22239?

No fix has been published for CVE-2026-22239 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-22239 being exploited?

There is no known exploitation of CVE-2026-22239 in the wild and no public exploit code.

## Other vulnerabilities in Bluspark Global BLUVOYIX

- [CVE-2026-22236](https://insights.sbomify.com/CVE-2026-22236/): Improper Authentication Vulnerability in BLUVOYIX (critical 10.0)
- [CVE-2026-22237](https://insights.sbomify.com/CVE-2026-22237/): Exposed Internal API Documentation Vulnerability in BLUVOYIX (critical 10.0)
- [CVE-2026-22238](https://insights.sbomify.com/CVE-2026-22238/): Administrator Account Creation Vulnerability in BLUVOYIX (critical 10.0)
- [CVE-2026-22240](https://insights.sbomify.com/CVE-2026-22240/): Plaintext Passwords Vulnerability in BLUVOYIX (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22239 and fix it if it is affected.

What it is: CVE-2026-22239 is a critical vulnerability in Bluspark Global BLUVOYIX, published on 14 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22239 in the wild and no public exploit code.

Affected product: Bluspark Global BLUVOYIX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22239/ (Markdown: https://insights.sbomify.com/CVE-2026-22239/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22239
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22239
- OSV: https://osv.dev/vulnerability/CVE-2026-22239

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22239/
Summaries are generated and may contain mistakes; the official description above is the record.