# CVE-2026-76962: Missing Authorization check in SAP S/4HANA (Manage Bank Chains app)

> Low-privilege attackers can delete unauthorized bank chain entries in SAP S/4HANA due to missing authorization checks, impacting availability.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **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:** 8 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-5jxw-c629-jw28

## What is CVE-2026-76962?

CVE-2026-76962 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA (Manage Bank Chains app), published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP S/4HANA (Manage Bank Chains app) does not perform sufficient authorization checks within certain affected functionality. An attacker with low privileges could send specially crafted requests to delete specific entries that should not be accessible to them. This results in a low impact on availability. There is no impact on confidentiality and integrity.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-76962 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76962 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4HANA (Manage Bank Chains app), published on 8 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-76962 in the wild and no public exploit code.

Affected product: SAP_SE SAP S/4HANA (Manage Bank Chains app). 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-76962/ (Markdown: https://insights.sbomify.com/CVE-2026-76962/index.md)
```

## Sources

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

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