{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-103512 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-103512 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-103512 is a medium-severity authentication bypass vulnerability in Perforce P4 (Helix Core), published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-103512 and fix it if it is affected.\n\nWhat it is: CVE-2026-103512 is a medium-severity authentication bypass vulnerability in Perforce P4 (Helix Core), published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-103512 in the wild and no public exploit code.\n\nAffected product: Perforce P4 (Helix Core). No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-103512/ (Markdown: https://insights.sbomify.com/CVE-2026-103512/index.md)","id":"CVE-2026-103512","markdown":"https://insights.sbomify.com/CVE-2026-103512/index.md","name":"CVE-2026-103512","record":{"aliases":["GHSA-mv4f-7chx-wrhv"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Perforce P4 Search","requires_auth":"low_privilege","summary":"Attackers with stolen tickets can bypass host-binding restrictions in P4 Search by spoofing client IPs, gaining unauthorized access as the ticket owner.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Perforce","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Ticket host-binding bypass via spoofed client IP in P4Search","id":"CVE-2026-103512","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Apache DataSketches","id":"CVE-2026-103513"},"packages":[],"prev":{"headline":"Arbitrary file-write via extension installation in P4Search","id":"CVE-2026-103511"},"products":["P4 (Helix Core)"],"published":"2026-10-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-05","vendors":["Perforce"]},"summary":"Attackers with stolen tickets can bypass host-binding restrictions in P4 Search by spoofing client IPs, gaining unauthorized access as the ticket owner.","url":"https://insights.sbomify.com/CVE-2026-103512/"}