Widely used Perforce P4 Server; unauthenticated access to repositories could disrupt software development and expose source code.
CVE-2026-6043
Unauthenticated access due to insecure defaults in P4 Server pre-2026.1.
Is CVE-2026-6043 being exploited?
Not confirmed. CVE-2026-6043 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.3% probability of exploitation in the next 30 days.
How severe is CVE-2026-6043?
CVE-2026-6043 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-6043?
Yes. A fix has been recorded for CVE-2026-6043. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-6043 affect?
CVE-2026-6043 affects P4 Server (Perforce Helix Core) pre-2026.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-6043?
Upgrade to 2026.1 and enforce secure defaults.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated creation of accounts, user enumeration, login with no password, and depot access, enabling source code exposure.
Patch when possible
- affected<= 2025.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.