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

> Authenticated operators can exploit SSRF in OCS Inventory NG to access internal network services or cloud metadata via unvalidated parameters.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/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-76177, GHSA-x3wr-4g6m-p8j5, UBUNTU-CVE-2026-76177

## What is CVE-2026-76177?

CVE-2026-76177 is a high-severity server-side request forgery 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

Server-Side Request Forgery (SSRF) vulnerability in the /ocsreports/?function=tele_activate endpoint due to insufficient validation of the HTTPS_SERV and FILE_SERV parameters. An authenticated user with operator privileges can provide arbitrary values for these parameters, causing the OCS Inventory server to make HTTP/HTTPS requests to external systems or internal resources, which could allow access to internal network services or metadata resources of cloud services.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-76177 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76177 is a high-severity server-side request forgery 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-76177 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-76177/ (Markdown: https://insights.sbomify.com/CVE-2026-76177/index.md)
```

## Sources

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

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