CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Called exploited the same day it was disclosed.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listingsame day
- Last sighting37d
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Jul 14, 2026
- EUVDENISA, European Unionlisted Jul 14, 2026
- VulnCheck KEVcommercial researchlisted Jul 14, 2026
- CIRCLaggregator, mirrors the abovelisted Jul 14, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationwww.acn.gov.it/portale/documents/20119/1300791/Operational_S
- reported exploitationblackpointcyber.com/blog/cve-analysis-july-2026/
- reported exploitationcydome.io/maritime-cybersecurity-bulletin-august-7th-2026/
- reported exploitationwww.recordedfuture.com/blog/july-2026-cve-landscape
- reported exploitationwww.cyfirma.com/research/tracking-ransomware-jul-2026/
- reported exploitationwww.resecurity.com/es/blog/article/from-wsproxy-to-root-inc-
14 public reports collected from VulnCheck and CIRCL, first on Jul 14, 2026. Each links to its original source. We have not verified them.
Description
Post-authentication improper control of generation of code ('Code Injection') vulnerability has been identified in the SMA1000 Appliance Management Console (AMC) which in specific conditions could potentially enable a remote authenticated attacker as administrator to execute arbitrary OS commands.
Required action (CISA)
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.
