CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 sighting38d
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Jul 27, 2026
- EUVDENISA, European Unionlisted Jul 27, 2026
- VulnCheck KEVcommercial researchlisted Jul 27, 2026
- CIRCLaggregator, mirrors the abovelisted Jul 27, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationwww.trellix.com/blogs/research/the-bug-report-august-2026-ed
- reported exploitationwww.recordedfuture.com/blog/july-2026-cve-landscape
- reported exploitationwww.resecurity.com/es/blog/article/cve-2026-16812-critical-c
- reported exploitationcydome.io/maritime-cybersecurity-bulletin-july-31st-2026/
- reported exploitationprevidian.com/CVE-2026-16812
- reported exploitationwww.arista.com/en/support/advisories-notices/security-adviso
7 public reports collected from VulnCheck and CIRCL, first on Jul 27, 2026. Each links to its original source. We have not verified them.
Description
VeloCloud Orchestrator (VCO) on-prem has a security issue where this issue may allow a remote attacker to access privileged internal functionality and impact the VCO host. Successful exploitation may compromise the confidentiality, integrity, and availability of the orchestrator and data managed by the orchestrator. This functionality was intended to be for internal use only and is not intended to be remotely accessible. Hosted and Dedicated versions of VCO have already been patched in advance of this notice going out. This issue was discovered externally and is known to be actively exploited.
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.
