CVE-2026-103512— Ticket host-binding bypass via spoofed client IP in P4Search
Quick assessment
Affected
Perforce P4 (Helix Core)
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.
在 Perforce P4 Search 2026.4.2 版本之前，系统在验证某些身份认证请求时，会信任客户端提供的地址。攻击者如果持有一个被盗的 P4 服务器凭证（ticket），可以绕过基于主机的凭证限制以及受信任地址控制机制，从而以该凭证所有者的身份访问 P4 Search。
Possible ATT&CK Techniques 1 AI
T1078 · Valid Accounts
Get alerts for future matching vulnerabilities
Log in to subscribe
I. Basic Information for CVE-2026-103512
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
Ticket host-binding bypass via spoofed client IP in P4Search
Source: CVE Program / CVE List V5
Vulnerability Description
Perforce P4 Search prior to 2026.4.2 trusts a client-supplied address when validating certain authentication requests. An attacker holding a stolen P4 Server ticket can bypass host-based ticket restrictions and trusted-address controls, gaining access to P4 Search as the ticket's owner.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Source: CVE Program / CVE List V5
Vulnerability Type
使用欺骗进行的认证绕过
Source: CVE Program / CVE List V5
Affected Products
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| Perforce | P4 (Helix Core) | 0 ~ 2026.4.1 | - |
|
II. Public POCs for CVE-2026-103512
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POC
Premium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2026-103512
请登录查看更多情报信息。
Other References for CVE-2026-103512 (1)
Same Patch Batch · Perforce · 2026-10-05 · 5 CVEs total
| CVE-2026-103510 | 9.5 CRITICAL | Authentication bypass via blank auth token in P4Search |
| CVE-2026-100102 | 9.5 CRITICAL | RCE via exposed JDWP debug agent in P4Search |
| CVE-2026-103507 | 7.5 HIGH | Arbitrary file-write via log configuration path in P4Search |
| CVE-2026-103511 | 5.1 MEDIUM | Arbitrary file-write via extension installation in P4Search |
IV. Related Vulnerabilities
Same product: P4 (Helix Core)
-
CVE-2026-103510
Authentication bypass via blank auth token in P4Search -
CVE-2026-103511
Arbitrary file-write via extension installation in P4Search -
CVE-2026-103507
Arbitrary file-write via log configuration path in P4Search -
CVE-2026-100102
RCE via exposed JDWP debug agent in P4Search -
CVE-2026-100103
Authentication bypass via default auth token in P4Search
Same vendor: Perforce
-
CVE-2026-103510
Authentication bypass via blank auth token in P4Search -
CVE-2026-103511
Arbitrary file-write via extension installation in P4Search -
CVE-2026-103507
Arbitrary file-write via log configuration path in P4Search -
CVE-2026-100102
RCE via exposed JDWP debug agent in P4Search -
CVE-2026-89212
XML External Entity in Akana API Platform
Same weakness: CWE-290
-
CVE-2026-105215
ZITADEL before 4.16.2 Account Pre-Hijacking via Forged Exter -
CVE-2026-104988
Pki-core: dogtag-pki: redhat-pki: pki: est fullcmc authentic -
CVE-2026-94422
xdg-dbus-proxy: message filtering bypass via reply serial al -
CVE-2026-104445
YesWiki before 4.6.7 Authentication Bypass via ActivityPub I -
CVE-2026-103347
WordPress hCaptcha for WP plugin <= 5.3.0 - Bypass Vulnerabi
V. Comments for CVE-2026-103512
No comments yet