Loading vulnerability…
CVE-2025-21127 is an uncontrolled search path element vulnerability in Adobe Photoshop Desktop affecting versions 25.12, 26.1, and earlier on Windows and macOS. The flaw allows the application to load a library from an attacker-influenced search path when resolving dependencies. By manipulating the search path environment so that Photoshop resolves a malicious library instead of the intended trusted one, an attacker can cause arbitrary code to execute when the vulnerable application starts or loads the affected component. The issue is classified as CWE-427 and requires the victim to run the vulnerable application.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical Adobe Photoshop vulnerability caused by improper search path validation that can lead to malicious code execution via a specially crafted file.
A critical arbitrary code execution vulnerability in Adobe Photoshop caused by an uncontrolled search path element.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.