# CVE-2026-71029: Information disclosure in Helidon

> Unauthenticated attackers can access critical data in Helidon Imperative Web Server via HTTP, requiring an upgrade to mitigate.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-f6h3-5c7w-257j

## What is CVE-2026-71029?

CVE-2026-71029 is a medium-severity vulnerability in Oracle Helidon, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Helidon product of Oracle Fusion Middleware (component: Imperative Web Server).  Supported versions that are affected are 3.0.0-3.2.17. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Helidon.  While the vulnerability is in Helidon, attacks may significantly impact additional products (scope change).  Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all Helidon accessible data. CVSS 3.1 Base Score 6.8 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Helidon.

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

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

## Is CVE-2026-71029 being exploited?

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

## Other vulnerabilities in Oracle Helidon

- [CVE-2026-73930](https://insights.sbomify.com/CVE-2026-73930/): Missing authorization in Helidon (critical 9.9)
- [CVE-2026-71074](https://insights.sbomify.com/CVE-2026-71074/): Auth bypass in Helidon (critical 9.8)
- [CVE-2026-71152](https://insights.sbomify.com/CVE-2026-71152/): Auth bypass in Helidon (critical 9.8)
- [CVE-2026-71164](https://insights.sbomify.com/CVE-2026-71164/): Auth bypass in Helidon (critical 9.8)
- [CVE-2026-73905](https://insights.sbomify.com/CVE-2026-73905/): Auth bypass in Helidon (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71029 is a medium-severity vulnerability in Oracle Helidon, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71029 in the wild and no public exploit code.

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

## Sources

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

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