How severe is CVE-2026-100102?

CVE-2026-100102 has a CVSS 4.0 base score of 9.5, rated critical severity.

Is CVE-2026-100102 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (27th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-100102?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2026-100102 published?

CVE-2026-100102 was published on 2026-10-05 and last updated on 2026-10-06.

CVE-2026-100102

CVE-2026-100102 is a critical-severity vulnerability with a CVSS 4.0 base score of 9.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-489.

Key facts

Severity: Critical (CVSS 4.0 base score 9.5)
EPSS exploit prediction: 0% (27th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-489
Published: 2026-10-05
Last modified: 2026-10-06

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.

Frequently asked questions

What is CVE-2026-100102?: 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.
How severe is CVE-2026-100102?: CVE-2026-100102 has a CVSS 4.0 base score of 9.5, rated critical severity.
Is CVE-2026-100102 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (27th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-100102?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-100102 published?: CVE-2026-100102 was published on 2026-10-05 and last updated on 2026-10-06.

References

https://portal.perforce.com/s/cve/a91Qi000003FE7NIAW/rce-via-exposed-jdwp-debug-agent-in-p4search

Other CWE-489 vulnerabilities

CVE-2023-4804 — Critical (CVSS 10.0): An unauthorized user could access debug features in Quantum HD Unity products that were accidentally exposed.
CVE-2026-49188 — Critical (CVSS 9.8): The ai_cmd utility executes with full root permissions. It pipes socket inputs directly to popen(), paving the way…
CVE-2024-46873 — Critical (CVSS 9.8): Multiple SHARP routers leave the hidden debug function enabled. An arbitrary OS command may be executed with the root…
CVE-2024-21785 — Critical (CVSS 9.8): A leftover debug code vulnerability exists in the Telnet Diagnostic Interface functionality of AutomationDirect P3-550E…
CVE-2024-32047 — Critical (CVSS 9.8): Hard-coded credentials for the CyberPower PowerPanel test server can be found in the production code. This might…
CVE-2024-28008 — Critical (CVSS 9.8): Active Debug Code in NEC Corporation Aterm WG1800HP4, WG1200HS3, WG1900HP2, WG1200HP3, WG1800HP3, WG1200HS2, WG1900HP,…

Browse all CWE-489 vulnerabilities →