CVE-2026-62640: Vulnerability in the Oracle Reports Developer product of Oracle Fusion Middleware (component: Security and...
Vulnerability in the Oracle Reports Developer product of Oracle Fusion Middleware (component: Security and Authentication). The supported version that is affected is 14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via IIOP to compromise Oracle Reports Developer. Successful attacks of this vulnerability can result in takeover of Oracle Reports Developer. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated attacker who can reach the IIOP service could take control of Oracle Reports Developer. The affected supported version is 14.1.2.0.0. A successful compromise could expose reports and credentials, permit unauthorized changes, and disrupt reporting services.
Executive priority
Treat this as an immediate remediation priority because compromise requires neither credentials nor user action and may cause complete takeover. Establish ownership, confirm exposure promptly, restrict IIOP reachability, and follow Oracle's advisory. Escalate any evidence of unauthorized access to incident response.
Technical view
CVE-2026-62640 is an improper access-control vulnerability (CWE-284) in Oracle Reports Developer's Security and Authentication component. It is remotely reachable through IIOP, requires no privileges or user interaction, and has low attack complexity. Oracle assigns CVSS 3.1 score 9.8, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited by the supplied evidence to Oracle Reports Developer 14.1.2.0.0. Risk is highest where IIOP is reachable from untrusted networks. The source bundle does not identify other affected versions, configurations, or products.
Exploitation context
The weakness is described as easily exploitable and capable of complete product takeover. However, the supplied KEV flag is false, and no cited source confirms active exploitation or public exploit availability. Treat exploit activity as unconfirmed, not absent.
Researcher notes
The record attributes the issue to Security and Authentication and classifies it as CWE-284, but provides no root-cause detail, affected code path, indicators, patch identifier, or safe detection signature. Avoid assuming broader Fusion Middleware impact. Consult Oracle's advisory and subsequent CVE updates for authoritative technical changes.
Mitigation direction
Check Oracle's advisory immediately for the authoritative patch or remediation instructions.
Apply Oracle-supported remediation after testing and according to your change-management process.
Restrict IIOP access to explicitly trusted systems where operationally feasible.
Isolate affected instances until remediation is verified if unnecessary network exposure cannot be removed.
Validation and detection
Inventory Oracle Reports Developer installations and confirm their exact versions.
Identify every network path that can reach IIOP on affected instances.
Verify Oracle-recommended remediation using version, patch, or configuration evidence.
Review relevant access and security logs for unexplained connections or unauthorized changes.
Confirm IIOP is inaccessible from untrusted network segments after mitigation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
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.
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.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.