Security readout for executives and security teams
Plain-English summary
Oracle Agile PLM 9.3.6 contains a critical security flaw that may let an unauthenticated, network-connected attacker read, create, change, or delete sensitive PLM data through HTTP. Availability is not identified as affected, but confidentiality and data integrity impacts could be severe.
Executive priority
Treat this as an immediate remediation priority because compromise could expose or corrupt all data accessible through affected PLM systems. Prioritize externally reachable deployments, restrict access while remediation is assessed, and require evidence that every 9.3.6 instance has been addressed.
Technical view
CVE-2026-61171 is an access-control and missing-authentication vulnerability affecting Oracle Agile PLM 9.3.6. It is remotely reachable over HTTP, requires no privileges or user interaction, and has low attack complexity. CVSS 3.1 is 9.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.
Likely exposure
Exposure exists where Oracle Agile PLM 9.3.6 is reachable over HTTP from untrusted networks. Internet-facing systems present the clearest concern, but attackers with internal network access may also reach affected deployments. The supplied sources do not identify other affected versions.
Exploitation context
The vulnerability is described as easily exploitable without authentication or user interaction. The supplied bundle does not report observed exploitation, and the CVE is not listed as KEV. Absence from KEV does not establish that exploitation has never occurred.
Researcher notes
The assigned weaknesses are CWE-284 and CWE-306, consistent with improper access control and missing authentication. The source material establishes remote unauthenticated impact but does not disclose the vulnerable endpoint, root cause, indicators, patch identifier, or public proof-of-concept. Avoid assuming availability impact; the supplied CVSS vector scores availability as none.
Mitigation direction
- Identify every Oracle Agile PLM deployment and confirm whether version 9.3.6 is running.
- Review Oracle's July 2026 advisory and apply its supported remediation guidance promptly.
- Restrict HTTP access to trusted networks and authorized administrative paths where operationally feasible.
- Increase monitoring for unauthorized PLM data access, creation, modification, or deletion.
- Protect critical PLM data with verified, access-controlled backups and recovery procedures.
Validation and detection
- Confirm installed Agile PLM versions using authoritative asset and configuration records.
- Verify whether affected HTTP interfaces are reachable from internet and untrusted internal networks.
- Confirm vendor-recommended remediation is applied consistently across all affected instances.
- Review application, identity, proxy, and network logs for unexplained unauthenticated activity.
- Validate critical data integrity and investigate unexpected record creation, modification, or deletion.
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 lookupCWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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-61171 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.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2oracleVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.