# CVE-2026-100103: Authentication bypass via default auth token in P4Search

> Unauthenticated attackers can use a default token to gain highest privileges and execute arbitrary code in Perforce P4 Search containers.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/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-crr7-cpqh-vjm5

## What is CVE-2026-100103?

CVE-2026-100103 is a critical vulnerability in Perfoce 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 reset the service authentication token to a publicly documented default value. An unauthenticated attacker with network access can obtain the highest application privilege, potentially leading to arbitrary code execution and compromise of the connected P4 Server.

Weakness: CWE-1392 (Use of Default Credentials)

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


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

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

## Is CVE-2026-100103 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100103 is a critical vulnerability in Perfoce 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-100103 in the wild and no public exploit code.

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

## Sources

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

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