# CVE-2026-6043: Insecure Default Configuration in P4 Server

> Insecure default settings in Perforce Helix Core Server allow unauthenticated attackers to create accounts, enumerate users, and access depot contents.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-rv45-r523-m576

## What is CVE-2026-6043?

CVE-2026-6043 is a high-severity vulnerability in Perforce Helix Core Server (P4D), published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

P4 Server versions prior to 2026.1 are configured with insecure default settings that, when exposed to untrusted networks, allow unauthenticated attackers to create arbitrary user accounts, enumerate existing users, authenticate to accounts with no password set, and access depot contents via the built-in 'remote' user. These default settings, taken together, can lead to unauthorized access to source code repositories and other managed assets. The 2026.1 release, expected in May 2026, enforces secure-by-default configurations on upgrade and new installations

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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


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

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

## Is CVE-2026-6043 being exploited?

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

Public exploit code:

- Perforce security research and tools - CVE-2026-6043 (github_poc): https://github.com/flyingllama87/p4wned

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6043 is a high-severity vulnerability in Perforce Helix Core Server (P4D), published on 24 Apr 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-6043 in the wild and no public exploit code.

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

## Sources

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

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