← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2026-75650 exploited? Yes: in CISA KEV since 8 Sep 2026

Gociux · Adobe Commerce and Magento · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2026-75650, Adobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 8 Sep 2026, 1 days after it was published. It affects Adobe Commerce and Magento. If you run it, CISA's required action is: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

exploitedYesCISA KEV · 8 Sep 2026
ransomwareNot knownno confirmed use
EPSStop 1%among the most likely CVEs to be exploited
severity10CVSS 3.1 · critical
US federal due11 Sep 2026BOD 22-01 deadline

What it is

Adobe Commerce and Magento Open Source contain an improper neutralization of special elements used in a template engine vulnerability that could allow an attacker to execute arbitrary code.

VendorAdobe (83 exploited CVEs in KEV)
ProductCommerce and Magento
VulnerabilityAdobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine Vulnerability
WeaknessCWE-1336
Published7 Sep 2026
Added to KEV8 Sep 2026
Reported by (CNA)adobe

What to do

  1. Check whether you run it. Look for Commerce and Magento in your asset inventory, including appliances and cloud images. Stack check lists every exploited Adobe CVE at once.
  2. Apply the fix. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 7 Sep 2026.
  4. Get told next time. Email alerts when CISA adds a CVE for Adobe.

Other exploited CVEs in Commerce and Magento

References

Questions

Is CVE-2026-75650 being exploited?

Yes. CISA added CVE-2026-75650 to the Known Exploited Vulnerabilities catalog on 8 Sep 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2026-75650 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2026-75650?

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Check Adobe's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Commerce and Magento and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in September 2026 · Adobe scorecard · act-now radar.

Running Adobe in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →