Security readout for executives and security teams
Plain-English summary
CVE-2026-70673 is a critical access-control vulnerability in Oracle Reports Developer 14.1.2.0.0. An unauthenticated attacker who can reach the service over HTTP may access critical information and alter or delete some accessible data. The impact may extend into connected products, although the supplied sources do not identify which products or environments are affected.
Executive priority
Treat this as an immediate remediation priority because exploitation requires only network access and no credentials. Assign owners to inventory, exposure reduction, vendor-guidance review, and incident-log review. Prioritize internet-facing and broadly reachable systems first, while recognizing that the supplied sources do not confirm active exploitation.
Technical view
The vulnerability affects Oracle Reports Developer 14.1.2.0.0, specifically Security and Authentication. It is remotely exploitable over HTTP without credentials or user interaction and is categorized as CWE-284. CVSS 3.1 is 9.3 with changed scope, high confidentiality impact, low integrity impact, and no stated availability impact.
Likely exposure
Exposure is highest where Oracle Reports Developer 14.1.2.0.0 accepts HTTP traffic from untrusted or broadly accessible networks. Internal deployments remain exposed to attackers who gain network reachability. The supplied evidence does not establish whether default configurations, particular endpoints, or authentication modes alter exploitability.
Exploitation context
The vulnerability is described as easily exploitable and requires no authentication, privileges, or user interaction. However, the supplied bundle marks it as absent from KEV and provides no evidence of active exploitation, public exploit code, or observed attacks. Absence from KEV does not prove that exploitation has not occurred.
Researcher notes
The record supplies no vulnerable endpoint, root cause details beyond CWE-284, proof of concept, patch identifier, or indicators of compromise. Scope change suggests effects may cross a security boundary, but affected downstream products are unspecified. Validation should remain defensive and rely on version, reachability, remediation status, and telemetry rather than intrusive exploitation.
Mitigation direction
- Identify Oracle Reports Developer 14.1.2.0.0 instances and their HTTP exposure immediately.
- Review Oracle's advisory for the vendor-approved patch or mitigation and apply it promptly.
- Restrict HTTP access to trusted administrative and application networks until remediation is confirmed.
- Increase monitoring for unusual access, data retrieval, and modification involving Reports Developer.
- Assess connected products and data stores because the vulnerability indicates cross-scope impact.
Validation and detection
- Confirm deployed Oracle Reports Developer versions using authoritative inventory and configuration records.
- Map every reachable HTTP path to affected instances, including internal and partner networks.
- Verify the Oracle-recommended remediation is installed and operational on each affected instance.
- Review relevant access and application logs for anomalous unauthenticated activity.
- Confirm network restrictions prevent untrusted systems from reaching affected HTTP services.
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-70673 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 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/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:C/C:H/I:L/A:N3.94.7oracleVulnerability scoring details
Base CVSS 3.1 score
9.3CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/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.