# CVE-2026-100102: RCE via exposed JDWP debug agent in P4Search

> Attackers can execute arbitrary code via an exposed unauthenticated Java debug interface in Perforce P4 Search containers, compromising the service account.

- **Severity:** Critical 9.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-9p2m-pch8-59mp

## What is CVE-2026-100102?

CVE-2026-100102 is a critical vulnerability in Perforce P4 (Helix Core), published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Perforce P4 Search container images prior to 2026.4.2 enable an unauthenticated Java debug interface. An attacker with network access to this interface can execute arbitrary code as the P4 Search service account, potentially leading to compromise of the connected P4 Server.

Weakness: CWE-489 (Active Debug Code)

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


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

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

## Is CVE-2026-100102 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100102 is a critical vulnerability in Perforce P4 (Helix Core), published on 5 Oct 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-100102 in the wild and no public exploit code.

Affected product: Perforce P4 (Helix Core). 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-100102/ (Markdown: https://insights.sbomify.com/CVE-2026-100102/index.md)
```

## Sources

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

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