# CVE-2026-101583: Vulnerability in the Helidon product of Oracle Fusion Middleware (component: helidon-common-mapper).


- **Severity:** High 7.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-rwcp-r2qc-9pgh

## What is CVE-2026-101583?

CVE-2026-101583 is a high-severity vulnerability in Oracle Corporation Helidon, published on 20 Oct 2026. 

### Official description

Vulnerability in the Helidon product of Oracle Fusion Middleware (component: helidon-common-mapper).  Supported versions that are affected are 4.0.0-4.5.5 and 27.0.0. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Helidon.  Successful attacks of this vulnerability can result in  unauthorized creation, deletion or modification access to critical data or all Helidon accessible data as well as  unauthorized read access to a subset of Helidon accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Helidon. CVSS 3.1 Base Score 7.0 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:L).

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2026-101583 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101583 is a high-severity vulnerability in Oracle Corporation Helidon, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-101583 in the wild and no public exploit code.

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

## Sources

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

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