# CVE-2026-127375: Vulnerability in the Oracle Hyperion Financial Close Management product of Oracle Hyperion (component: Reconciliation Manage).


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-qmq6-v79g-rcvm

## What is CVE-2026-127375?

CVE-2026-127375 is a medium-severity vulnerability in Oracle Hyperion Financial Close Management, published on 17 Nov 2026. 

### Official description

Vulnerability in the Oracle Hyperion Financial Close Management product of Oracle Hyperion (component: Reconciliation Manage).   The supported version that is affected is 11.2.26.0.000. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Hyperion Financial Close Management.  Successful attacks of this vulnerability can result in  unauthorized read access to a subset of Oracle Hyperion Financial Close Management accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/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-127375?


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

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

## Is CVE-2026-127375 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-127375 is a medium-severity vulnerability in Oracle Hyperion Financial Close Management, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-127375 in the wild and no public exploit code.

Affected product: Oracle Hyperion Financial Close Management. 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-127375/ (Markdown: https://insights.sbomify.com/CVE-2026-127375/index.md)
```

## Sources

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

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