CVE-2026-34632: Photoshop Installer | CWE-427: Uncontrolled Search Path Element
Adobe Photoshop Installer was affected by an Uncontrolled Search Path Element vulnerability that could have resulted in arbitrary code execution in the context of the current user. An attacker could have exploited this vulnerability by placing a malicious library in a directory searched by the installer. Exploitation of this issue required user interaction in that a victim must have been running the installer. Scope is changed.
Security readout for executives and security teams
Plain-English summary
This issue affects the Adobe Photoshop Installer, as described in the provided sources. If a user ran the vulnerable installer while a malicious library was in a searched directory, attacker code could run as that user. The impact is high, but exploitation requires user interaction and local file-placement conditions.
Executive priority
Prioritize this for software deployment and endpoint-management teams. The issue can lead to code execution with high business impact, but the practical risk depends on how installers are sourced, stored, and run inside the organization.
Technical view
CVE-2026-34632 is a CWE-427 uncontrolled search path issue in Adobe Photoshop Installer. The CVSS 3.1 score is 8.6 with local attack vector, low complexity, no privileges required, required user interaction, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Organizations are most exposed where users download or run Photoshop installers manually, from shared folders, removable media, or unmanaged software repositories. The source bundle lists affected version data only as version "0" and does not provide CPEs, so exact product-version exposure is incomplete.
Exploitation context
The sources state exploitation requires a victim to run the installer after a malicious library is placed in a directory searched by it. KEV is false, and the supplied sources do not state active exploitation in the wild.
Researcher notes
Key evidence gaps remain: the bundle does not identify specific installer build numbers, patch status, or exploitation telemetry. Treat the CVSS and Talos report as the main technical anchors, and avoid broad claims about Photoshop application exposure beyond the installer.
Mitigation direction
Check Adobe and Talos guidance for corrected installer availability and exact affected builds.
Use only Photoshop installers obtained from Adobe-controlled distribution channels.
Remove untrusted installer copies from shared folders and endpoint download locations.
Restrict software installation workflows to managed deployment tooling where practical.
Monitor endpoint alerts for unexpected library loads during installer execution.
Validation and detection
Inventory endpoints and software repositories containing Photoshop installer packages.
Confirm installer provenance against vendor guidance before allowing execution.
Review recent endpoint telemetry for suspicious library loads near installer launches.
Check whether users ran Photoshop installers from writable or shared directories.
Track Adobe or Talos updates for clarified affected versions and remediation details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-427: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-427 · source CWE mapping
Uncontrolled Search Path Element
Uncontrolled Search Path Element represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.