Skip to main content
ExploitedIn CISA KEVFix available

CVE-2026-16812

Exploitation confirmed. First attested on 2026-07-27 by CISA-ADP, CISA KEV, GCVE · kevintel.

  • Published2026-07-27
  • Fixed in6.4.2.4 · 6.1.3.4 · 5.2.3.14
  • WeaknessCWE-78

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-07-27Added to the CISA KEV catalogCISA KEV
  2. 2026-07-27Listed as exploited by GCVEGCVE
  3. 2026-07-27Exploitation first reportedCISA KEV
  4. 2026-07-2716:17CVE publishedNVD
  5. 2026-07-2719:45SSVC exploitation set to activeCISA-ADP

Observed activity

isMalicious corpus · updated 2026-10-28 03:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-16812?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-16812?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Arista velocloud orchestrator
BranchAffectedFixed in
6.4≥ 6.4.0, < 6.4.2.46.4.2.4
6.1≥ 6.1.0, < 6.1.3.46.1.3.4
5.2≥ 5.2.0, < 5.2.3.145.2.3.14
7.0= 7.0.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Arista velocloud orchestrator to 6.4.2.4 · 6.1.3.4 · 5.2.3.14
  2. CISA’s required action: 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.due 2026-07-30

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

CISA Known Exploited Vulnerability

Date Added
2026-07-27
Patch Due Date
2026-07-30
Ransomware Use
Unknown
Required Action
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.

Sources

  • NVDCVE recordread 2026-10-24
  • CISA KEVKEV entry2026-07-27
  • GCVEexploitation2026-07-27
  • CISA-ADPSSVC decisionactive2026-07-27
  • OpenCVESSVC decisionactive—
  • CNACVSS 4.010read 2026-10-24
  • CNACVSS 3.110read 2026-10-24
  • CNAweakness (CWE)CWE-78read 2026-10-24
  • FIRST EPSSEPSS score1.0 %2026-10-26

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:X/R:X/V:X/RE:X/U:X
Published
2026-07-27
Last Modified
2026-10-24
NVD status
Analyzed

Frequently asked questions

What is CVE-2026-16812?

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.

Is CVE-2026-16812 actively exploited?

Yes. CVE-2026-16812 is on the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning it has been confirmed as actively exploited in the wild. CISA requires federal agencies to patch by 2026-07-30.

What is the CVSS score for CVE-2026-16812?

CVE-2026-16812 has a CVSS v3 base score of 10 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, July 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database