{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-103511 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-103511 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-103511 is a medium-severity path traversal vulnerability in Perforce P4 (Helix Core), published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-103511 and fix it if it is affected.\n\nWhat it is: CVE-2026-103511 is a medium-severity path traversal vulnerability in Perforce P4 (Helix Core), published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-103511 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-103511/ (Markdown: https://insights.sbomify.com/CVE-2026-103511/index.md)","id":"CVE-2026-103511","markdown":"https://insights.sbomify.com/CVE-2026-103511/index.md","name":"CVE-2026-103511","record":{"aliases":["GHSA-49f3-gp89-25v9"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Perforce P4 Search","requires_auth":"high_privilege","summary":"Privileged attackers can write arbitrary files to the installation directory via extension installation, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Perforce","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"}],"description":"Perforce P4 Search prior to 2026.4.2 does not validate file names supplied to its extension installation feature. An attacker with super-user or service-token privileges can write files with arbitrary content to the P4 Search installation directory.","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":"Arbitrary file-write via extension installation in P4Search","id":"CVE-2026-103511","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Ticket host-binding bypass via spoofed client IP in P4Search","id":"CVE-2026-103512"},"packages":[],"prev":{"headline":"Authentication bypass via blank auth token in P4Search","id":"CVE-2026-103510"},"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":"Privileged attackers can write arbitrary files to the installation directory via extension installation, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-103511/"}