CVE-2026-127394 json
Vulnerability in the Product Lifecycle Analytics product of Oracle Supply Chain (component: Installation Issues).
published 7h ago modified 6h ago also EUVD-2026-128095
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Vulnerability in the Product Lifecycle Analytics product of Oracle Supply Chain (component: Installation Issues). The supported version that is affected is 3.6.1. Difficult to exploit vulnerability allows low privileged attacker with logon to the infrastructure where Product Lifecycle Analytics executes to compromise Product Lifecycle Analytics. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Product Lifecycle Analytics, 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 Product Lifecycle Analytics accessible data as well as unauthorized access to critical data or complete access to all Product Lifecycle Analytics accessible data. CVSS 3.1 Base Score 7.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N).
Is CVE-2026-127394 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N |
| NVD | 3.1 | 7.2 | CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N |
Affected products
- Oracle Corporation Product Lifecycle Analytics
References
-
oracle.com
/security-alerts/cspunov2026.html
vendor-advisory
Sources
- CVE List CVE-2026-127394
- NVD CVE-2026-127394
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.