# CVE-2025-26658: Broken Authentication in SAP Business One (Service Layer)

> Attackers can bypass authentication to impersonate users and escalate privileges, allowing unauthorized data access and modification in SAP Business One.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A: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:** 11 Mar 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-3fjr-h35g-vfc9

## What is CVE-2025-26658?

CVE-2025-26658 is a medium-severity authentication bypass vulnerability in SAP_SE SAP Business One (Service Layer), published on 11 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Service Layer in SAP Business One, allows attackers to potentially gain unauthorized access and impersonate other users in the application to perform unauthorized actions. Due to the improper session management, the attackers can elevate themselves to higher privilege and can read, modify and/or write new data. To gain authenticated sessions of other users, the attacker must invest considerable time and effort. This vulnerability has a high impact on the confidentiality and integrity of the application with no effect on the availability of the application.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2025-26658?


## How do I fix CVE-2025-26658?

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

## Is CVE-2025-26658 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-26658 and fix it if it is affected.

What it is: CVE-2025-26658 is a medium-severity authentication bypass vulnerability in SAP_SE SAP Business One (Service Layer), published on 11 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-26658 in the wild and no public exploit code.

Affected product: SAP_SE SAP Business One (Service Layer). 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-2025-26658/ (Markdown: https://insights.sbomify.com/CVE-2025-26658/index.md)
```

## Sources

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

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