CVE-2026-16812
This CVE is being exploited. Apply the vendor fix, or take the service off the internet until you can, then check your logs for attempts.
What it is
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.
Live exploitation on the huntback network (30 days)
Detection
Evidence
Exploited (reported). CISA added it to KEV 118 days ago.
Published
Added to CISA Known Exploited Vulnerabilities
Observed: our own decoys saw it. Reported: CISA, the vendor or another named source says so. Weaponised: public exploit code or a scanner template exists. Methodology
Questions
Is CVE-2026-16812 being exploited in the wild?
Yes. It is listed in the CISA Known Exploited Vulnerabilities catalogue. Our decoy network has not captured an attempt yet.
Can CVE-2026-16812 be detected on the network?
huntback has no wire signature for CVE-2026-16812 yet; it may need local or authenticated access to exploit.
How huntback helps
Deploy a decoy that emulates Velocloud Orchestrator and you will see every attempt at this CVE the moment it lands, with the full payload, the attacker's infrastructure, and any stage-2 loader. Then huntback can scan the attacker back.
Related
NVD record → Browse all CVEs → Live malware and C2 finds → Novel-attack discovery → Deploy a decoy →API
This record, with its evidence timeline, as JSON:
curl -H "X-API-Key: $HUNTBACK_KEY" https://app.huntback.io/api/v1/evidence/CVE-2026-16812