Security readout for executives and security teams
Plain-English summary
Oracle Product Lifecycle Analytics 3.6.1 contains a critical access-control vulnerability. Someone already able to log on to its underlying infrastructure could access, create, delete, or modify critical application data without application authentication. Compromise may also affect other products, although the sources do not identify which ones.
Executive priority
Treat confirmed 3.6.1 deployments as an urgent remediation priority, especially where many users can access the hosting infrastructure. The primary business risk is theft or manipulation of critical lifecycle data. Escalate immediately if suspicious infrastructure logins or unexplained data changes are found.
Technical view
CVE-2026-61174 is a CWE-284 access-control vulnerability with CVSS 3.1 score 9.0. The vector indicates local access, low complexity, no privileges or user interaction, changed scope, and high confidentiality and integrity impact. Availability impact is not claimed. The only identified affected supported version is 3.6.1.
Likely exposure
Exposure is limited to Oracle Product Lifecycle Analytics 3.6.1 installations where an attacker can log on to the hosting infrastructure. Internet reachability alone is not identified as sufficient. Infrastructure accounts, shared administrative environments, and compromised local credentials increase practical risk.
Exploitation context
The supplied sources do not report active exploitation, and the CVE is not marked as CISA KEV. Exploitation is described as easy but requires infrastructure logon. No public exploit availability, attack indicators, or observed campaign details are provided.
Researcher notes
The apparent authentication distinction matters: PR:N describes application privileges, while AV:L and Oracle's wording require logon to the execution infrastructure. Scope change suggests effects beyond the vulnerable component, but affected downstream products are unspecified. Public evidence does not establish exploitation, exploit availability, indicators, or a specific corrected version.
Mitigation direction
- Identify every Oracle Product Lifecycle Analytics deployment and confirm its exact version.
- Review Oracle's July 2026 advisory and apply the vendor-specified correction or upgrade guidance.
- Restrict infrastructure logon to essential, trusted administrators until remediation is complete.
- Review and reduce local accounts, privileged access, and shared credentials on affected hosts.
- Increase monitoring for unauthorized access or changes to Product Lifecycle Analytics data.
Validation and detection
- Confirm whether version 3.6.1 is installed using trusted inventory and deployment records.
- Verify the vendor-recommended correction is applied according to Oracle guidance.
- Review infrastructure login records for unexpected accounts, sources, or access times.
- Examine application audit records for unauthorized viewing, creation, deletion, or modification of critical data.
- Assess connected products and trust boundaries because the CVSS scope is changed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-61174 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N2.55.8oracleVulnerability scoring details
Base CVSS 3.1 score
9CriticalVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Oracle AdvisoryCVE reference, oracle · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.