# CVE-2026-76971: Server-Side Request Forgery in SAP Manufacturing Integration and Intelligence

> An attacker can exploit SSRF in SAP Manufacturing Integration to trigger arbitrary outbound requests and potentially execute scripts via XML processing.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-fcc6-f47w-v8rx

## What is CVE-2026-76971?

CVE-2026-76971 is a medium-severity server-side request forgery vulnerability in SAP_SE SAP Manufacturing Integration and Intelligence, published on 8 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Due to a Server-Side Request Forgery (SSRF) vulnerability in SAP Manufacturing Integration and Intelligence, an attacker could cause the server to initiate arbitrary outbound requests. If processed by the application, this behavior could be combined with XML/XSL processing to enable execution of scripts. Successful exploitation could result in a low impact on the confidentiality, integrity, and availability of the application.

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

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


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

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

## Is CVE-2026-76971 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76971 is a medium-severity server-side request forgery vulnerability in SAP_SE SAP Manufacturing Integration and Intelligence, published on 8 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-76971 in the wild and no public exploit code.

Affected product: SAP_SE SAP Manufacturing Integration and Intelligence. 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-76971/ (Markdown: https://insights.sbomify.com/CVE-2026-76971/index.md)
```

## Sources

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

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