# CVE-2025-53051: Information disclosure in Oracle Database Server

> High-privileged attackers can read unauthorized data from the RDBMS Functional Index component in Oracle Database Server.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Oct 2025
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-27cf-pmx7-3wpg

## What is CVE-2025-53051?

CVE-2025-53051 is a low-severity vulnerability in Oracle Database Server, published on 21 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vulnerability in the RDBMS Functional Index component of Oracle Database Server.  Supported versions that are affected are 23.4-23.9. Easily exploitable vulnerability allows high privileged attacker having SYSDBA privilege with network access via Oracle Net to compromise RDBMS Functional Index.  Successful attacks of this vulnerability can result in  unauthorized read access to a subset of RDBMS Functional Index accessible data. CVSS 3.1 Base Score 2.7 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N).

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-53051?

It affects 1 product.


Products: Oracle Database Server.

## How do I fix CVE-2025-53051?

No fix has been published for CVE-2025-53051 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-53051 being exploited?

There is no known exploitation of CVE-2025-53051 in the wild and no public exploit code.

Public exploit code:

- proof of concept for CVE-2025-53051 (github_poc): https://github.com/emad-almousa/CVE-2025-53051

## Other vulnerabilities in Oracle Database Server

- [CVE-2015-4863](https://insights.sbomify.com/CVE-2015-4863/): Other in n/a (critical 10.0)
- [CVE-2013-1534](https://insights.sbomify.com/CVE-2013-1534/): Other in n/a (critical 10.0)
- [CVE-2010-0071](https://insights.sbomify.com/CVE-2010-0071/): Other in n/a (critical 10.0)
- [CVE-2009-1979](https://insights.sbomify.com/CVE-2009-1979/): Other in n/a (critical 10.0)
- [CVE-2009-1985](https://insights.sbomify.com/CVE-2009-1985/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53051 and fix it if it is affected.

What it is: CVE-2025-53051 is a low-severity vulnerability in Oracle Database Server, published on 21 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53051 in the wild and no public exploit code.

Affected product: Oracle Database Server. 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-2025-53051/ (Markdown: https://insights.sbomify.com/CVE-2025-53051/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53051
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53051
- OSV: https://osv.dev/vulnerability/CVE-2025-53051

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53051/
Summaries are generated and may contain mistakes; the official description above is the record.