# CVE-2026-0496: Multiple vulnerabilities in SAP Fiori App (Intercompany Balance Reconciliation)

> High-privilege attackers can upload arbitrary files, including scripts, due to missing validation in SAP Fiori Intercompany Balance Reconciliation.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2026
- **Updated:** 13 Jan 2026
- **Also known as:** GHSA-5j28-xwjp-v5gv

## What is CVE-2026-0496?

CVE-2026-0496 is a medium-severity vulnerability in SAP_SE SAP Fiori App (Intercompany Balance Reconciliation), published on 13 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SAP Fiori App Intercompany Balance Reconciliation allows an attacker with high privileges  to upload any file (including script files) without proper file format validation. This has low impact on confidentiality, integrity and availability of the application.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-0496 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0496 is a medium-severity vulnerability in SAP_SE SAP Fiori App (Intercompany Balance Reconciliation), published on 13 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0496 in the wild and no public exploit code.

Affected product: SAP_SE SAP Fiori App (Intercompany Balance Reconciliation). 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-0496/ (Markdown: https://insights.sbomify.com/CVE-2026-0496/index.md)
```

## Sources

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

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