☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
Oracle logo [ WEBSITE ] [ VENDOR STATS ]
CVSS: 7.3 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N 🐛 CWE-284
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2026-87260

CVE-2026-87260 Supply Chain Attack in Oracle
📅 PUBLISHED: 2026-09-15 00:00 UTC 🔄 UPDATED: 2026-09-22 09:09 UTC
[ ZERO-DAY / UNPATCHED ] [ DEFENSE PATCH ↓ ]
💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.30%
👁️
0.30% probability
7.4× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1190
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
Country: United States License: Commercial
VULNERABLE: 6.2.1
CVSS VECTOR BREAKDOWN 7.3
AV: A Attack Vector Adjacent
AC: L Attack Complexity Low
PR: L Privileges Required Low
UI: N User Interaction None
S: U Scope Unchanged
C: H Confidentiality High
I: H Integrity High
A: N Availability None
7.3
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2026-87260 is an easily exploitable vulnerability in Oracle Agile Engineering Data Management (component: Engineering Communication Interface), affecting supported version 6.2.1. A low-privileged attacker with access to the physical communication segment attached to the host running the product can compromise the application, resulting in unauthorized creation, deletion, or modification of critical data and full read access to application-accessible data. No public proof-of-concept, exploit code, or vendor patch is currently available.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Technical Analysis

Oracle Agile Engineering Data Management (Agile eDMS) is an enterprise PLM (product lifecycle management) platform used to manage engineering data, bills of materials, change orders, and product records across supply chain and manufacturing workflows. The affected component, the Engineering Communication Interface, handles the exchange of engineering data between Agile eDMS and connected systems on the communication segment to which the host is attached.

The NVD description classifies this as a "easily exploitable" flaw that requires only low privileges (PR:L) and adjacent network access (AV:A), with no user interaction (UI:N). The CVSS 3.1 vector (CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) indicates:

  • Attack Vector (A): The attacker must be on the same physical communication segment as the Agile eDMS host, or have a network position that can reach it. This reduces remote exploitability compared to a network-vector (AV:N) vulnerability but is realistic for shared corporate LANs, VLANs, or inter-connect segments used by engineering and supply chain systems.
  • Attack Complexity (L): No special conditions or race windows are required; the flaw can be triggered consistently.
  • Privileges Required (L): The attacker needs a low-privileged account or position — not administrative access to the product.
  • User Interaction (N): No victim action is required, making it suitable for automated or scripted attacks.
  • Scope (U): The impact remains confined to the Agile eDMS security authority.
  • Confidentiality (H): Complete read access to all Agile eDMS-accessible data.
  • Integrity (H): Unauthorized creation, deletion, or modification of critical data.
  • Availability (N): No direct availability impact is stated.

The vulnerability class is an access control weakness in the Engineering Communication Interface. While the exact implementation detail is not disclosed in the NVD description, the characteristics (adjacent access, low privilege, no UI, high confidentiality and integrity impact) are consistent with a broken authorization or access-control check that allows a low-privileged actor to reach data or operations intended for higher-privileged users. The description does not disclose specific endpoints, parameters, function names, or API paths; no such details are fabricated here.

Because the CNA title field is empty and no CWE identifier is provided in the source data, the precise coding defect remains unconfirmed. The CWE assignment above (CWE-284) is an inference based on the access-control characteristics of the described impact, not a vendor-confirmed classification, and should be treated as provisional.

Exploitation Scenarios

The following attack chain is inferred strictly from the vulnerability class and the NVD description. No public proof-of-concept exists; no specific function names, endpoints, or parameters are asserted.

  1. Reconnaissance / target identification. The attacker identifies an Oracle Agile eDMS 6.2.1 instance reachable on a shared physical communication segment (for example, an engineering VLAN or a supply chain integration segment) where the Engineering Communication Interface service is exposed. Target identification can be performed by scanning the adjacent segment for hosts responding with Agile-specific service banners or web interfaces.

  2. Privilege foothold. The attacker obtains or holds a low-privileged account or a low-privileged network position on the same segment. The vulnerability requires only low privileges (PR:L), so no administrative credential is needed.

  3. Triggering the flaw class. The attacker sends crafted requests or data exchanges to the Engineering Communication Interface that exploit the broken access-control condition. Because user interaction is not required and attack complexity is low, the request can be issued directly and repeatedly. At the class level, the attacker bypasses or satisfies the flawed authorization check to gain the ability to read and manipulate engineering data they should not be able to reach.

  4. Post-exploitation impact. Successful exploitation gives the attacker high confidentiality and high integrity impact: reading complete application-accessible data (product designs, BOMs, change records, supplier and engineering communications) and creating, deleting, or modifying critical records. There is no availability impact, so the platform itself remains operational while data integrity is silently compromised.

No exploit code, PoC, or Nuclei template is available for this CVE. Any detection or hunting must therefore rely on behavioral and access-pattern anomalies rather than signature-based exploit indicators.

Impact Assessment

The business impact centers on data confidentiality and integrity in a PLM platform that frequently stores sensitive intellectual property: engineering drawings, bill-of-materials structures, change orders, supplier data, and product lifecycle records. Compromise allows a low-privileged adjacent attacker to read all of that data and to alter or delete it, which can propagate into downstream manufacturing, procurement, and supply chain processes that consume Agile eDMS records.

Affected system: Oracle Agile Engineering Data Management 6.2.1, Engineering Communication Interface component. Blast radius is scoped by the CVSS vector (S:U) to the Agile eDMS security authority, but the data consumed downstream may extend well beyond the application itself. The absence of availability impact (A:N) means the incident may be silent until data integrity discrepancies are discovered manually.

CVSS 3.1 base score is 7.3 (High), driven by C:H/I:H, with AV:A, AC:L, PR:L, UI:N. No EPSS score has been published by FIRST.org, no CISA KEV listing exists, and no exploit code or public PoC is available. Patch confidence is 0/4 — no fix evidence was found in any tracked source.

Detection Guidance

Sigma Rule

title: Suspicious Access Pattern Against Oracle Agile eDMS Engineering Communication Interface
id: 8f4c2b90-6d3a-4c1e-9a77-2e5b0c7a1d44
status: experimental
description: Detects anomalous or unauthorized access patterns to the Engineering Communication Interface of Oracle Agile Engineering Data Management 6.2.1, indicative of access-control abuse by a low-privileged adjacent actor.
references:
  - https://nvd.nist.gov/vuln/detail/CVE-2026-87260
author: valtersit.com
date: 2026/01/01
tags:
  - attack.t1190
logsource:
  category: webserver
  product: oracle
detection:
  selection_component:
    cs-uri-stem|contains:
      - '/EngineeringCommunicationInterface'
      - '/eci'
  selection_anomaly:
    sc-status:
      - 200
      - 500
    c-ip|notin:
      - '10.0.0.0/8'
  condition: selection_component and selection_anomaly
falsepositives:
  - Legitimate engineering data exchanges from trusted integration hosts
level: high

YARA Rule

rule CVE_2026_87260_Agile_eDMS_Exploit_Artifacts
{
    meta:
        description = "Detects artifacts or scripts referencing Oracle Agile eDMS Engineering Communication Interface exploitation (CVE-2026-87260)"
        author = "valtersit.com"
        date = "2026-01-01"
        reference = "https://nvd.nist.gov/vuln/detail/CVE-2026-87260"
        severity = "high"

    strings:
        $a = "Engineering Communication Interface" ascii nocase
        $b = "Agile Engineering Data Management" ascii nocase
        $c = "CVE-2026-87260" ascii nocase
        $d = "Agile eDMS" ascii nocase

    condition:
        any of ($a, $b, $c, $d)
}

Suricata IDS Rule

alert tcp any any -> any any (msg:"CVE-2026-87260 - Suspicious Access to Oracle Agile eDMS Engineering Communication Interface"; flow:established,to_server; content:"EngineeringCommunicationInterface"; http_uri; nocase; content:"Agile"; http_header; nocase; sid:2026872600; rev:1; metadata:created_at 2026_01_01, cve CVE-2026-87260, confidence low; classtype:attempted-user;)

Elastic Detection

sequence by source.ip with maxspan=5m
  [ network where network.protocol == "http" and url.path : "*EngineeringCommunicationInterface*"
      and not source.ip : "10.0.0.0/8" ]
  [ network where network.protocol == "http" and url.path : "*EngineeringCommunicationInterface*"
      and http.response.status_code == 200 ]

Splunk SPL Query

index=web OR index=proxy
| search (uri_path="*EngineeringCommunicationInterface*" OR uri_path="*/eci*")
| eval is_internal=if(match(src_ip, "^(10\.|192\.168\.|172\.(1[6-9]|2[0-9]|3[01])\.)"), "internal", "external")
| stats count values(http_status) as statuses dc(uri_path) as distinct_paths by src_ip, is_internal, dest_host
| where (is_internal="external" AND count > 5) OR distinct_paths > 10
| sort - count

Wazuh OSSEC Rule

<group name="oracle,agile,cve_2026_87260,">
  <rule id="2026872" level="12">
    <if_sid>31100</if_sid>
    <field name="url">EngineeringCommunicationInterface|/eci</field>
    <description>CVE-2026-87260: Possible unauthorized access to Oracle Agile eDMS Engineering Communication Interface</description>
    <mitre>
      <id>T1190</id>
    </mitre>
    <group>access_control,plm,</group>
  </rule>
</group>

Mitigation & Patch Guidance

Patch confidence: 0/4 — UNPATCHED. No vendor fix, workaround, or patched version reference was found in any tracked source for CVE-2026-87260.

  1. Immediate mitigations.

    • Segment the Agile eDMS host and the Engineering Communication Interface onto a dedicated VLAN, isolated from general user and guest networks, strictly limiting who is on the same physical communication segment (matches the CVSS AV:A precondition).
    • Restrict low-privileged accounts and enforce least privilege; review and reduce any accounts that can reach the Engineering Communication Interface.
    • Apply host and network firewall ACLs so that only explicitly trusted integration hosts can reach the Engineering Communication Interface service.
    • Increase logging and monitoring over the Engineering Communication Interface and alert on anomalous read/write patterns.
  2. Patch / upgrade steps.

    • No patch is currently available. Monitor Oracle's Critical Patch Update (CPU) and Security Alert channels for a fix referencing CVE-2026-87260 or Oracle Agile Engineering Data Management 6.2.1.
    • Track the Oracle Advisory and NVD entry for patch references; apply immediately once published.
  3. Long-term hardening.

    • Implement continuous monitoring of data integrity in Agile eDMS (unexpected record creation, deletion, or modification).
    • Enforce network segmentation and zero-trust principles around PLM integration segments.
    • Reduce the population of accounts with access to the Engineering Communication Interface and rotate credentials of integration accounts.
    • Subscribe to Oracle security notifications and re-evaluate the CVSS vector as vendor details emerge.

References

No threat actor campaigns or exploit-in-the-wild evidence are associated with CVE-2026-87260 in the available data. No public PoC, exploit code, or Nuclei template exists at time of writing.

◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2026-87260/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.