# CVE-2026-35266: Cross-site request forgery in Oracle REST Data Services > A CSRF vulnerability in Oracle REST Data Services allows attackers to modify or access data and cause partial denial of service via user interaction. - **Severity:** High 7.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 28 May 2026 - **Updated:** 29 May 2026 - **Also known as:** GHSA-g57p-44cp-pjf5 ## What is CVE-2026-35266? CVE-2026-35266 is a high-severity vulnerability in Oracle REST Data Services, published on 28 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description Vulnerability in Oracle REST Data Services (component: Core). Supported versions that are affected are 24.2.0-26.1.0. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTPS to compromise Oracle REST Data Services. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle REST Data Services, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle REST Data Services accessible data as well as unauthorized access to critical data or complete access to all Oracle REST Data Services accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle REST Data Services. CVSS 3.1 Base Score 7.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:L). Weakness: CWE-400 (Uncontrolled Resource Consumption), CWE-352 (Cross-Site Request Forgery) ## Which versions are affected by CVE-2026-35266? It affects 1 product. Products: Oracle Rest Data Services. ## How do I fix CVE-2026-35266? No fix has been published for CVE-2026-35266 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-35266 being exploited? There is no known exploitation of CVE-2026-35266 in the wild and no public exploit code. ## Other vulnerabilities in Oracle REST Data Services - [CVE-2026-46840](https://insights.sbomify.com/CVE-2026-46840/): Auth bypass in Oracle REST Data Services (critical 10.0) - [CVE-2026-46775](https://insights.sbomify.com/CVE-2026-46775/): Denial of service in Oracle REST Data Services (critical 9.9) - [CVE-2026-46839](https://insights.sbomify.com/CVE-2026-46839/): Auth bypass in Oracle REST Data Services (critical 9.9) - [CVE-2026-35277](https://insights.sbomify.com/CVE-2026-35277/): Missing authorization in Oracle REST Data Services (high 8.1) - [CVE-2026-46829](https://insights.sbomify.com/CVE-2026-46829/): Denial of service in Oracle REST Data Services (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-35266 and fix it if it is affected. What it is: CVE-2026-35266 is a high-severity vulnerability in Oracle REST Data Services, published on 28 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-35266 in the wild and no public exploit code. Affected product: Oracle REST Data Services. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-35266/ (Markdown: https://insights.sbomify.com/CVE-2026-35266/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35266 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35266 - OSV: https://osv.dev/vulnerability/CVE-2026-35266 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-35266/ Summaries are generated and may contain mistakes; the official description above is the record.