# CVE-2026-61043: Missing authorization in Oracle Production Scheduling

> Low-privileged attackers can modify or read critical data in Oracle Production Scheduling via a missing authorization flaw requiring user interaction.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-77q4-m5g2-wrpv

## What is CVE-2026-61043?

CVE-2026-61043 is a medium-severity missing authorization vulnerability in Oracle E-Business Suite, published on 21 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle Production Scheduling product of Oracle E-Business Suite (component: Internal Operations).  Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Production Scheduling executes to compromise Oracle Production Scheduling.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Production Scheduling, 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 Production Scheduling accessible data as well as  unauthorized read access to a subset of Oracle Production Scheduling accessible data. CVSS 3.1 Base Score 6.7 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:H/A:N).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle E-Business Suite.

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

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

## Is CVE-2026-61043 being exploited?

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

## Other vulnerabilities in Oracle E-Business Suite

- [CVE-2026-46817](https://insights.sbomify.com/CVE-2026-46817/): Oracle E-Business Suite Improper Privilege Management (critical 9.8, exploited in the wild)
- [CVE-2022-21587](https://insights.sbomify.com/CVE-2022-21587/): Oracle E-Business Suite Unspecified (critical 9.8, exploited in the wild)
- [CVE-2015-4798](https://insights.sbomify.com/CVE-2015-4798/): Other in n/a (critical 10.0)
- [CVE-2015-4839](https://insights.sbomify.com/CVE-2015-4839/): Other in n/a (critical 10.0)
- [CVE-2008-1826](https://insights.sbomify.com/CVE-2008-1826/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61043 is a medium-severity missing authorization vulnerability in Oracle E-Business Suite, published on 21 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-61043 in the wild and no public exploit code.

Affected product: Oracle E-Business Suite. 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-61043/ (Markdown: https://insights.sbomify.com/CVE-2026-61043/index.md)
```

## Sources

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

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