Is CVE-2026-60917 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-60917 being exploited in the wild.

How severe is CVE-2026-60917?

High severity, with a CVSS score of 8.1, published 21 July 2026.

Which products and versions are affected?

Oracle Corporation Inventory Management 12.2.3-12.2.15.

Is there a fix for CVE-2026-60917?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-60917 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-60917?

Check whether you run Oracle Corporation Inventory Management at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-60917: Oracle Inventory Management data compromise in Core Receiving

CVE-2026-60917 · Severity: high · CVSS 8.1 · Published 2026-07-21

A vulnerability exists in the Core Receiving component of Oracle Inventory Management, a tool used by businesses to track stock and supply chain operations. A user with low-level access to the system can exploit this flaw over the network to view, modify, or delete sensitive inventory data. This could lead to significant disruptions in supply chain accuracy, unauthorized changes to stock records, and the exposure of proprietary business information.

Technologies: Oracle Corporation Inventory Management. Vendors: Oracle Corporation.

Quick answers

Is CVE-2026-60917 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-60917 being exploited in the wild.
How severe is CVE-2026-60917?: High severity, with a CVSS score of 8.1, published 21 July 2026.
Which products and versions are affected?: Oracle Corporation Inventory Management 12.2.3-12.2.15.
Is there a fix for CVE-2026-60917?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-60917 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-60917?: Check whether you run Oracle Corporation Inventory Management at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability in the Core Receiving component of Oracle Inventory Management (part of Oracle E-Business Suite) allows for unauthorized data access and modification. The flaw is easily exploitable by a low-privileged attacker with network access via HTTP. Successful exploitation grants the attacker the ability to create, delete, or modify all accessible data within the Inventory Management module, as well as read-only access to critical data. The vulnerability affects versions 12.2.3 through 12.2.15. It is tracked as part of the Oracle Critical Patch Update (CPU) for July 2026.

Affected products

Oracle Corporation Oracle Inventory Management (Oracle E-Business Suite) 12.2.3-12.2.15

Timeline

2026-07-21: disclosed: Initial disclosure via Oracle Critical Patch Update and NVD publication.

References

https://www.oracle.com/security-alerts/cpujul2026.html

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.