{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-103510 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-103510 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-103510 is a critical authentication bypass vulnerability in Perforce P4 (Helix Core), published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-103510 and fix it if it is affected.\n\nWhat it is: CVE-2026-103510 is a critical authentication bypass vulnerability in Perforce P4 (Helix Core), published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-103510 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-103510/ (Markdown: https://insights.sbomify.com/CVE-2026-103510/index.md)","id":"CVE-2026-103510","markdown":"https://insights.sbomify.com/CVE-2026-103510/index.md","name":"CVE-2026-103510","record":{"aliases":["GHSA-rgmx-jfh8-6fx8"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Perforce P4 Search","requires_auth":"none","summary":"An unauthenticated attacker can bypass authentication in P4 Search when the token is blank, gaining highest privileges and compromising the connected P4 Server.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Perforce","cpe":[],"cvss":{"score":9.5,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-636","name":"Not Failing Securely"}],"description":"P4 Search prior to 2026.4.2 does not fail securely when its service authentication token is blank. In affected configurations, an unauthenticated attacker with network access can obtain the highest application privilege, potentially leading to compromise of P4 Search and the connected P4 Server.","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":"Authentication bypass via blank auth token in P4Search","id":"CVE-2026-103510","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":"Arbitrary file-write via extension installation in P4Search","id":"CVE-2026-103511"},"packages":[],"prev":{"headline":"Credential Disclosure in P4 Search Configuration API","id":"CVE-2026-103509"},"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":"total"},"state":"PUBLISHED","updated":"2026-10-05","vendors":["Perforce"]},"summary":"An unauthenticated attacker can bypass authentication in P4 Search when the token is blank, gaining highest privileges and compromising the connected P4 Server.","url":"https://insights.sbomify.com/CVE-2026-103510/"}