# CVE-2026-60941: Missing authorization in Oracle Service Fulfillment Manager

> High-privileged attackers can bypass authorization to read, create, delete, or modify critical data in Oracle Service Fulfillment Manager.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-jf2r-ppwp-632c

## What is CVE-2026-60941?

CVE-2026-60941 is a high-severity missing authorization vulnerability in Oracle Service Fulfillment Manager, published on 21 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vulnerability in the Oracle Service Fulfillment Manager product of Oracle E-Business Suite (component: Fulfillment Engine).  Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Service Fulfillment Manager.  While the vulnerability is in Oracle Service Fulfillment Manager, attacks may significantly impact additional products (scope change).  Successful attacks of this vulnerability can result in  unauthorized creation, deletion or modification access to critical data or all Oracle Service Fulfillment Manager accessible data as well as  unauthorized access to critical data or complete access to all Oracle Service Fulfillment Manager accessible data. CVSS 3.1 Base Score 8.7 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N).

Weakness: CWE-284 (Improper Access Control), CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Oracle Service Fulfillment Manager.

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

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

## Is CVE-2026-60941 being exploited?

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

## Other vulnerabilities in Oracle Service Fulfillment Manager

- [CVE-2017-3284](https://insights.sbomify.com/CVE-2017-3284/): Cross-site scripting in Service Fulfillment Manager (high 8.2)
- [CVE-2017-3285](https://insights.sbomify.com/CVE-2017-3285/): Cross-site scripting in Service Fulfillment Manager (high 8.2)
- [CVE-2026-60942](https://insights.sbomify.com/CVE-2026-60942/): Missing authorization in Oracle Service Fulfillment Manager (high 8.1)
- [CVE-2026-70786](https://insights.sbomify.com/CVE-2026-70786/): Missing authorization in Oracle Service Fulfillment Manager (high 7.6)
- [CVE-2026-60943](https://insights.sbomify.com/CVE-2026-60943/): Privilege escalation in Oracle Service Fulfillment Manager (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-60941 is a high-severity missing authorization vulnerability in Oracle Service Fulfillment Manager, published on 21 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-60941 in the wild and no public exploit code.

Affected product: Oracle Service Fulfillment Manager. 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-60941/ (Markdown: https://insights.sbomify.com/CVE-2026-60941/index.md)
```

## Sources

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

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