Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent network segment access
-
ExploitReach Engineering Communication Interface
-
ExecutionWin timing/complexity condition
-
ImpactRead critical engineering data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to have access to the physical communication segment attached to the hardware where Oracle Agile Engineering Data Management 6.2.1 executes (adjacent network, AV:A) and to interact with the Engineering Communication Interface component; no credentials are needed (PR:N) and no user interaction is required (UI:N). The significant limiting factors are the adjacency requirement (an attacker on the public Internet cannot reach it) and high attack complexity (AC:H), indicating the attacker must satisfy timing or configuration conditions outside their direct control. Impact is limited to confidentiality (C:H) - unauthorized read of critical data - with no integrity or availability effect. |
| Impact | This is a moderate-severity information-disclosure flaw (CVSS 3.1 base 5.3) whose real-world risk is substantially lower than the confidentiality-only 'C:H' impact might suggest, because the exploitation preconditions are demanding. The vector CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N requires an adjacent-network position - specifically access to the physical communication segment attached to the host - combined with high attack complexity (AC:H), meaning the attacker must win a race or satisfy conditions outside their control. No EPSS score was provided in the input, so exploitation probability cannot be quantified. The vulnerability is NOT listed in CISA KEV and no public exploit code was supplied, so exploitation status is 'no public exploit identified at time of analysis.' There is a signal conflict worth flagging: the input Tags include 'Authentication Bypass,' but the Oracle description characterizes this as unauthorized read access to critical data via an adjacent-network attacker, not as a bypass of an authentication control - treat the 'Authentication Bypass' tag as unverified. Overall this is a genuine but low-urgency issue: patch in the normal Oracle CPU cycle rather than as an emergency, given AV:A + AC:H and no evidence of exploitation. |
| Exploit ScenarioDerived | An attacker who has already gained a foothold on the same physical/adjacent network segment as the Oracle Agile Engineering Data Management server intercepts or manipulates traffic to the Engineering Communication Interface under favorable timing conditions, extracting critical engineering data without authenticating. The adjacent-vector (AV:A) and high-complexity (AC:H) requirements mean the attacker needs local network proximity and must satisfy conditions not fully under their control. No public proof-of-concept was provided in the intelligence sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Oracle Agile Engineering Data Management 6.2.1 exposes critical data to unauthorized reads through its Engineering Communication Interface when an attacker is positioned on the physical communication segment serving the host. The flaw is unauthenticated (PR:N) and needs no user interaction (UI:N), but requires adjacency (AV:A) plus high attack complexity (AC:H), so it is only reachable by someone already on the local network segment rather than from the public Internet. Impact is confidentiality-only - no integrity or availability effect - and no public exploit has been identified at time of analysis; Oracle addressed it in its October 2026 Critical Patch Update.
RemediationAI
Apply the Oracle Critical Patch Update for October 2026 (https://www.oracle.com/security-alerts/cpuoct2026.html), which is the vendor's published remediation for this CVE; the provided intelligence does not include a discrete post-6.2.1 build number, so treat the CPU as the authoritative patch source and confirm the exact replacement binary or patch set with Oracle Support before scheduling the upgrade. Because the patch data indicates availability only at advisory level, validate that the CPU actually covers your Agile EDM 6.2.1 installation rather than assuming it does. Where patching must be deferred, the highest-value compensating control is network segmentation: place Agile EDM hosts and, in particular, the Engineering Communication Interface listener on a dedicated VLAN with strict ingress filtering so that only known engineering workstations and integration endpoints can reach the segment, since the attack requires adjacency and blocking lateral access removes the precondition entirely - the trade-off is that misconfigured ACLs will break legitimate engineering-tool integrations, so baseline traffic first. As a second layer, host-based firewalling on the Agile EDM server should allow the Engineering Communication Interface port only from an explicit allow-list of peer addresses, and any unused or non-essential ECI endpoints should be disabled in configuration; both reduce exposure but add administrative overhead and require change control. Do not rely on authentication hardening as a mitigation, since the vector is PR:N and credentials are not part of the exploitation path.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the Engineering Communication Interface within Oracle Supply Chain's Agile Engineering Data Management (Agile EDM) product family, the PLM/data-management tier used to hold engineering bills of material, item masters and change records. The CVSS 3.1 vector AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N describes an adjacent-network attack path: the attacker must sit on the same physical communication segment as the host running Agile EDM and interact with the Engineering Communication Interface to induce an information leak. AC:H indicates that success depends on conditions outside the attacker's direct control - timing, protocol state or a specific deployment configuration - rather than a straightforward request/response. No CWE identifier was published with the CVE, but the observable behavior (privilege-free read of data the attacker should not see, with no write or denial-of-service effect) is consistent with an access-control or information-exposure weakness in the interface's request handling. Because the scope is unchanged (S:U) and only confidentiality is impacted, the flaw cannot be chained internally to compromise other components, which caps its blast radius at data the Agile EDM instance itself can read.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Adjacent-segment access gives AV:A, the stated difficulty gives AC:H, no auth needed gives PR:N, and impact is confidentiality-only so I:N and A:N.
Primary rating from Vendor (oracle).
CVSS VectorVendor: oracle
DescriptionCVE.org
Vulnerability in the Oracle Agile Engineering Data Management product of Oracle Supply Chain (component: Engineering Communication Interface). The supported version that is affected is 6.2.1. Difficult to exploit vulnerability allows unauthenticated attacker with access to the physical communication segment attached to the hardware where the Oracle Agile Engineering Data Management executes to compromise Oracle Agile Engineering Data Management. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Agile Engineering Data Management accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N).
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-106142
GHSA-rpwf-g4wv-g8rx
NVD
CVE.org
EPSS
Exploit-DB