{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-103509 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-103509 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-103509 is a high-severity vulnerability in Perforce P4 (Helix core), published on 15 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-103509 and fix it if it is affected.\n\nWhat it is: CVE-2026-103509 is a high-severity vulnerability in Perforce P4 (Helix core), published on 15 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-103509 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-103509/ (Markdown: https://insights.sbomify.com/CVE-2026-103509/index.md)","id":"CVE-2026-103509","markdown":"https://insights.sbomify.com/CVE-2026-103509/index.md","name":"CVE-2026-103509","record":{"aliases":["GHSA-m94h-8qfm-w394"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Perforce P4 Search","requires_auth":"high_privilege","summary":"Administrative users can retrieve stored credentials in cleartext via the configuration API, enabling privilege escalation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Perforce","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-1220","name":"Insufficient Granularity of Access Control"}],"description":"P4 Search (formerly Helix Search) returns stored credentials in cleartext through its configuration API to users with administrative privileges on the connected P4 Server, allowing privilege escalation.\nThis affects 2026.4.2 and earlier and is fixed in 2026.4.3.","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":"Credential Disclosure in P4 Search Configuration API","id":"CVE-2026-103509","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Authentication bypass via blank auth token in P4Search","id":"CVE-2026-103510"},"packages":[],"prev":{"headline":"Path traversal via logging configuration in P4Search","id":"CVE-2026-103508"},"products":["P4 (Helix core)"],"published":"2026-10-15","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-15","vendors":["Perforce"]},"summary":"Administrative users can retrieve stored credentials in cleartext via the configuration API, enabling privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-103509/"}