# CVE-2026-40136: Denial of service (DoS) in SAP Financial Consolidation

> An authenticated attacker can temporarily disconnect other users, causing a denial of service in SAP Financial Consolidation.

- **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:** 12 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-296w-48hc-3xvf

## What is CVE-2026-40136?

CVE-2026-40136 is a medium-severity denial of service vulnerability in SAP_SE SAP Financial Consolidation, published on 12 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP Financial Consolidation allows an authenticated attacker to disconnect other users by terminating their sessions temporarily preventing access. However, the application itself cannot be compromised resulting in a low impact on availability. There is no impact on confidentiality and integrity of the data

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2026-40136 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40136 is a medium-severity denial of service vulnerability in SAP_SE SAP Financial Consolidation, published on 12 May 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-40136 in the wild and no public exploit code.

Affected product: SAP_SE SAP Financial Consolidation. 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-40136/ (Markdown: https://insights.sbomify.com/CVE-2026-40136/index.md)
```

## Sources

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

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