# CVE-2026-8339: SQL Injection in Coverity Connect SOAP API

> An authenticated attacker can exploit SQL injection in the SOAP API to read database contents and execute unauthorized commands.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-9cc8-j46r-gq7j

## What is CVE-2026-8339?

CVE-2026-8339 is a high-severity SQL injection vulnerability in Black Duck Coverity Connect, published on 29 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A SQL injection vulnerability exists in the Coverity Connect SOAP API for versions between 2024.6.0 and 2026.3.0 (inclusive). A malicious, authenticated threat actor who sends a specially crafted payload can achieve full read access to database contents and other unauthorized commands.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-8339 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8339 is a high-severity SQL injection vulnerability in Black Duck Coverity Connect, published on 29 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8339 in the wild and no public exploit code.

Affected product: Black Duck Coverity Connect. 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-8339/ (Markdown: https://insights.sbomify.com/CVE-2026-8339/index.md)
```

## Sources

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

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