PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-101370 Oracle Corporation CVE debrief

A vulnerability in Oracle REST Data Services (component: Core) allows an unauthenticated attacker with network access via HTTP to compromise Oracle REST Data Services. Successful attacks require human interaction from a person other than the attacker and can result in unauthorized read access to a subset of Oracle REST Data Services accessible data.

Vendor
Oracle Corporation
Product
Oracle REST Data Services
CVSS
LOW 3.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-20
Original CVE updated
2026-10-20
Advisory published
2026-10-20
Advisory updated
2026-10-20

Who should care

Defenders responsible for Oracle REST Data Services, including operators, platform administrators, vulnerability management teams, and security teams, should assess exposure and prioritize verification of versions 24.2.0-26.1.0 to prevent potential unauthorized read access.

Why it matters

The vulnerability in Oracle REST Data Services allows an unauthenticated attacker to potentially access sensitive data, requiring defenders to assess exposure and prioritize verification of affected versions.

  • Potential unauthorized read access to Oracle REST Data Services data
  • Requires verification of Oracle REST Data Services versions 24.2.0-26.1.0
  • Human interaction from a person other than the attacker is required for successful attacks

Technical summary

The vulnerability in Oracle REST Data Services (component: Core) allows an unauthenticated attacker with network access via HTTP to compromise Oracle REST Data Services. Successful attacks require human interaction from a person other than the attacker and can result in unauthorized read access to a subset of Oracle REST Data Services accessible data. The CVSS 3.1 Base Score is 3.1 (Confidentiality impacts).

Defensive priority

Assess exposure and prioritize verification of Oracle REST Data Services versions 24.2.0-26.1.0 for potential unauthorized read access.

Recommended defensive actions

  • Assess exposure of Oracle REST Data Services versions 24.2.0-26.1.0
  • Prioritize verification of potential unauthorized read access
  • Review Oracle advisory for additional information
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and Oracle advisory provide details on the vulnerability, but additional information on exploitation or impact is limited. Defenders should verify versions 24.2.0-26.1.0 and assess potential unauthorized read access with network access via HTTP. Human interaction from a person other than the attacker is required for successful attacks.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-101370 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-101370

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-101370 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-101370

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • CVE-2026-101370

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/101xxx/CVE-2026-101370.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://www.oracle.com/security-alerts/cpuoct2026.html

    Supplemental source - vendor-advisory

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.