# CVE-2026-114948: Information disclosure in MySQL Cluster

> A low-privileged local attacker can read a subset of MySQL Cluster data via the JS module; MySQL Cluster operators should patch.

- **Severity:** Low 2.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-355j-hf43-pgpg

## What is CVE-2026-114948?

CVE-2026-114948 is a low-severity information disclosure vulnerability in Oracle Corporation MySQL Cluster, published on 17 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: JS module).  Supported versions that are affected are 8.0.0-8.0.50, 8.4.0-8.4.13, 9.7.0-9.7.4 and  26.10. Difficult to exploit vulnerability allows low privileged attacker with logon to the infrastructure where MySQL Cluster executes to compromise MySQL Cluster.  Successful attacks of this vulnerability can result in  unauthorized read access to a subset of MySQL Cluster accessible data. CVSS 3.1 Base Score 2.5 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-114948?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-114948?

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

## Is CVE-2026-114948 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114948 and fix it if it is affected.

What it is: CVE-2026-114948 is a low-severity information disclosure vulnerability in Oracle Corporation MySQL Cluster, published on 17 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-114948 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Oracle Corporation MySQL Cluster. 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-114948/ (Markdown: https://insights.sbomify.com/CVE-2026-114948/index.md)
```

## Sources

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

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