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
CVE-2026-6043
“—” beside the score: it is equal to NVD's CVSS score.
This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 1.3% (69th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-25415 (ENISA EUVD) · GHSA-rv45-r523-m576 (GitHub Security Advisories)Source: ENISA EUVD
- Public exploit or proof-of-concept code is available
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
The CVE record's CNA (Perforce) lists Perforce Helix Core Server (P4D) versions up to and including 2025.2 as affected. No release containing a fix is confirmed on record.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHmedium confidence
- EG Risk
- 71EG Risk 71/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity88% × 45%Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix. - EPSS PROB
- 1.3%
- EPSS %ILE
- 69th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 1.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
April 24, 2026
Last Modified
October 26, 2026
Advisory Details (2)
Auto-updated May 2, 2026Perforce Support Portal
https://portal.perforce.com/s/cve/a91Qi000002wRUvIAM/insecure-default-configuration-in-p4-serverImportant security update: Secure by default
https://help.perforce.com/helix-core/server-apps/p4sag/current/Content/P4SAG/secure-by-default-overview.htmlWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 44× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 98 of 245 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 147 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 1.3% · 69th percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 1.3% · 69th percentile
- 2026-10-27 21:07 UTCEG score recompute
- 2026-10-27 21:07 UTCGHSA enrichmentGHSA-rv45-r523-m576 · GitHub severity HIGH
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 1.3% · 69th percentile
- 2026-10-26 21:31 UTCEG score recompute
- 2026-10-26 21:31 UTCGHSA enrichmentGHSA-rv45-r523-m576 · GitHub severity HIGH
- 2026-10-26 16:32 UTCEPSS rescoreEPSS 1.3% · 69th percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 1.3% · 69th percentile
- 2026-10-25 14:15 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 1.3% · 69th percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 1.3% · 69th percentile
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 1.3% · 69th percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 1.3% · 69th percentile
- 2026-10-21 03:56 UTCEG score recompute
- 2026-10-21 03:56 UTCGHSA enrichmentGHSA-rv45-r523-m576 · GitHub severity HIGH
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 1.3% · 69th percentile
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-18 03:26 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-16 16:43 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 1.3% · 68th percentile
Show 73 moreShow fewer
- 2026-10-13 15:18 UTCEG score recompute
- 2026-10-13 15:18 UTCGHSA enrichmentGHSA-rv45-r523-m576 · GitHub severity HIGH
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-12 15:51 UTCEG score recompute
- 2026-10-11 19:35 UTCEG score recompute
- 2026-10-11 16:50 UTCEG score recompute
- 2026-10-11 14:12 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-02 17:56 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-09-28 13:52 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-09-21 21:09 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 1.3% · 68th percentile
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-11 09:37 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-08 22:01 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-05 15:31 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-04 05:07 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-09-01 04:40 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-28 21:42 UTCEPSS rescoreEPSS 1.3% · 66th percentile
- 2026-08-26 14:47 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-25 13:49 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-23 00:19 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-21 23:49 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-20 22:56 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-19 17:04 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-18 13:49 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-17 14:53 UTCEG score recompute
- 2026-08-17 14:53 UTCGHSA enrichmentGHSA-rv45-r523-m576 · GitHub severity HIGH
- 2026-08-17 13:47 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-16 14:56 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-16 05:49 UTCEG score recompute
- 2026-08-16 05:49 UTCGHSA enrichmentGHSA-rv45-r523-m576 · GitHub severity HIGH
- 2026-08-16 02:15 UTCEPSS rescoreEPSS 1.3% · 67th percentile
- 2026-08-15 01:31 UTCEPSS rescoreEPSS 1.3% · 66th percentile
- 2026-08-14 17:03 UTCGHSA enrichmentGHSA-rv45-r523-m576 · GitHub severity HIGH
- 2026-08-14 04:09 UTCEG score recompute
- 2026-08-14 04:09 UTCGHSA enrichmentGHSA-rv45-r523-m576 · GitHub severity HIGH
- 2026-08-13 22:00 UTCEPSS rescoreEPSS 1.3% · 66th percentile
- 2026-08-13 08:32 UTCGHSA enrichmentGHSA-rv45-r523-m576 · GitHub severity HIGH
- 2026-08-12 17:53 UTCEG score recompute
- 2026-08-12 17:53 UTCGHSA enrichmentGHSA-rv45-r523-m576 · GitHub severity HIGH
- 2026-08-12 13:51 UTCEPSS rescoreEPSS 1.3% · 66th percentile
- 2026-08-11 16:42 UTCEG score recompute
- 2026-08-11 16:42 UTCGHSA enrichmentGHSA-rv45-r523-m576 · GitHub severity HIGH
- 2026-08-11 02:10 UTCEG score recompute
- 2026-08-11 02:10 UTCGHSA enrichmentGHSA-rv45-r523-m576 · GitHub severity HIGH
- 2026-08-11 00:00 UTCEPSS rescoreEPSS 1.3% · 66th percentile
- 2026-08-10 04:44 UTCGHSA enrichmentGHSA-rv45-r523-m576 · GitHub severity HIGH
- 2026-08-09 16:03 UTCEG score recompute
- 2026-08-09 16:03 UTCGHSA enrichmentGHSA-rv45-r523-m576 · GitHub severity HIGH
- 2026-08-09 13:47 UTCEPSS rescoreEPSS 1.3% · 66th percentile
Publicly available exploits
(1 reference)Public exploit code is referenced for this CVE (1 GitHub PoC). No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.
- GitHub PoCflyingllama87/p4wnedPublished Apr 3, 2026
Perforce security research and tools - CVE-2026-6043
Open source ↗
Related CVEs(same CWE)
Same CWE
10 shownCWE-1188
Frequently asked(5)
What is CVE-2026-6043?
When was the CVE record for CVE-2026-6043 published?
Is CVE-2026-6043 actively exploited?
What is the CVSS score of CVE-2026-6043?
How do I remediate CVE-2026-6043?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-6043
Is Your Infrastructure Affected by CVE-2026-6043?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.