# CVE-2026-76175: Multiple vulnerabilities in Ocsreports for OCS Inventory NG

> An authenticated operator can exploit SQL injection in Ocsreports to extract sensitive information from the database.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/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:** 3 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-76175, GHSA-w845-9495-33qx, UBUNTU-CVE-2026-76175

## What is CVE-2026-76175?

CVE-2026-76175 is a high-severity SQL injection vulnerability in Ocsreports, published on 3 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in the del_check parameter of the /ocsreports/?function=save_query_list endpoint. Input provided by an authenticated user with operator privileges is incorporated into an SQL query without proper parameterisation or validation, allowing the query to be manipulated and information to be extracted from the database using SQL injection techniques.

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

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


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

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

## Is CVE-2026-76175 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76175 is a high-severity SQL injection vulnerability in Ocsreports, published on 3 Sep 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-76175 in the wild and no public exploit code.

Affected product: Ocsreports. 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-76175/ (Markdown: https://insights.sbomify.com/CVE-2026-76175/index.md)
```

## Sources

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

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