{"id":"CVE-2026-61169","url":"https://www.cyber-defence.io/tools/cve/CVE-2026-61169","generatedAt":"2026-10-28T00:28:15.378Z","title":"Vulnerability in the Oracle Agile PLM product of Oracle Supply Chain (component: Security).","description":"Vulnerability in the Oracle Agile PLM product of Oracle Supply Chain (component: Security).   The supported version that is affected is 9.3.6. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Agile PLM executes to compromise Oracle Agile PLM.  While the vulnerability is in Oracle Agile PLM, attacks may significantly impact additional products (scope change).  Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all Oracle Agile PLM accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).","published":"2026-07-21T22:18:49.000Z","lastModified":"2026-10-24T15:10:00.000Z","status":"Analyzed","sourceIdentifier":"secalert_us@oracle.com","cvss":{"version":"3.1","score":6.5,"severity":"MEDIUM","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N"},"cwe":["CWE-284"],"affected":["oracle/agile product lifecycle management"],"epss":{"score":0.00154,"percentile":0.0452,"date":"2026-10-26","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"low","text":"Lower severity and a low EPSS score (0.15%). Track it; it rarely justifies an emergency change on its own."},"changes":[],"references":[{"url":"https://www.oracle.com/security-alerts/cpujul2026.html","tags":["Vendor Advisory"],"source":"secalert_us@oracle.com"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-61169","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}