Today's picture
Arista confirmed active zero-day exploitation of CVE-2026-16812, a maximum-severity command injection in VeloCloud Orchestrator on-premises deployments that exposes the orchestrator host and all managed SD-WAN Edge devices, with CISA adding it to KEV today and setting a two-day federal deadline of July 30. JetBrains disclosed CVE-2026-63077, a CVSS 9.8 unauthenticated remote code execution flaw in TeamCity On-Premises that affects every version the company has ever shipped, reachable through the agent polling protocol by any attacker with HTTP access. And CISA added CVE-2025-68686 to KEV, confirming active exploitation of a Fortinet FortiOS patch bypass that restores the attack surface of SSL-VPN vulnerabilities exploited continuously since 2022.
Today's intelligence
3 items
01
CriticalArista VeloCloudCISA KEV
Arista VeloCloud Orchestrator has a CVSS 10.0 command injection zero-day being actively exploited, with a two-day federal deadline and Edge device exposure downstream
VeloCloud Orchestrator is the management plane for enterprise SD-WAN. Compromising it does not stop at the orchestrator host. Arista explicitly warns that attackers may then reach all managed Edge devices. The on-premises exposure cannot be eliminated through configuration alone.
CVECVE-2026-16812
CVSS10.0 (maximum)
KEV addedJuly 28, 2026
Fed deadlineJuly 30, 2026
Fixed inVCO 5.2.3.14
6.1.3.4, 6.4.2.4
7.0.0.1
What happened
Arista Networks published Security Advisory 0144 on Monday disclosing CVE-2026-16812, an OS command injection vulnerability in VeloCloud Orchestrator On-Premises that carries CVSS scores of 10.0 under both v3.1 and v4.0 frameworks. The flaw allows a remote unauthenticated attacker to reach privileged internal functionality in the orchestrator that was designed for internal use only and was never intended to be externally accessible. Arista confirmed the vulnerability was discovered externally and is known to be actively exploited in the wild. No credentials, no authentication token, and no user interaction are required. The CVSS vector is fully network-accessible, low complexity, no privileges required, and no user interaction needed, with high confidentiality, integrity, and availability impact on both the orchestrator and surrounding scope. Arista explicitly warns that compromises to the VCO platform may allow attackers access to VeloCloud Edge devices and urges customers who identify a compromised orchestrator to rotate credentials, review administrator activity, validate managed device state, and restore or replace affected instances from trusted sources. The flaw affects VeloCloud Orchestrator On-Prem across its supported release branches. Fixed versions are 5.2.3.14, 6.1.3.4, 6.4.2.4, and 7.0.0.1. Hosted and dedicated cloud VCO deployments were patched before the advisory was published. On-premises deployments are the only affected class. CISA added CVE-2026-16812 to its Known Exploited Vulnerabilities catalog today and set a federal remediation deadline of July 30, one of the shortest windows CISA has set this year alongside the two-day Check Point deadline from Issue 92. The CISA KEV entry includes a specific forensics triage requirement, citing its guidance on forensic triage methods that should accompany remediation when exploitation is confirmed.
Why it matters
VeloCloud Orchestrator is the management and configuration plane for VeloCloud SD-WAN networks. An attacker who compromises the orchestrator does not merely have access to the orchestrator host itself. They have access to the configuration of every SD-WAN Edge device managed through it, including the ability to modify routing policies, create tunnels, and potentially push configuration changes to all branch and datacenter edge nodes. Arista's own advisory names Edge device access as a post-exploitation concern. The attack surface is the management plane for an organization's wide area network.
Don't miss
Arista's advisory states the on-premises exposure cannot be removed through configuration. Unlike network appliance vulnerabilities where restricting management interface exposure removes the attack surface entirely, this flaw is in functionality that is inherently reachable through the orchestrator's normal operating posture. Patch is the only full mitigation. Organizations running end-of-support VCO versions should note that Arista has not assessed whether those versions are vulnerable, which in practice means they should be treated as vulnerable and prioritized for upgrade before patching supported releases.
Potential actions
- Patch VeloCloud Orchestrator On-Premises to 5.2.3.14, 6.1.3.4, 6.4.2.4, or 7.0.0.1 immediately. The federal deadline is July 30. Do not defer to the next maintenance window given confirmed active exploitation.
- Follow the CISA forensics triage guidance attached to this KEV entry. Confirmed exploitation means some deployments were breached before today. Review orchestrator access logs for anomalous commands and configuration changes, audit all managed Edge device states, and rotate credentials for the orchestrator and any connected systems.
- If running an end-of-support VCO version, treat it as vulnerable and prioritize upgrade. Arista has not assessed those versions, which is not the same as confirming they are safe.
The Sip
Maximum CVSS. Zero-day exploitation confirmed. Two-day federal deadline. The orchestrator sits above every Edge device in the SD-WAN. Compromising it is not a single-node incident. Patch by Wednesday and check whether anyone was through the door before you locked it.
02
CriticalJetBrains TeamCityCI/CD
TeamCity On-Premises has a CVSS 9.8 unauthenticated RCE affecting every version ever shipped, reachable via the build agent polling protocol
The attack path is the channel TeamCity uses to talk to build agents. An attacker with HTTP access and no credentials sends a crafted payload to that endpoint and executes commands under the TeamCity server process. Code, secrets, pipeline configurations, and stored credentials are all in scope.
CVECVE-2026-63077
CVSS9.8
AffectsAll TeamCity
On-Premises versions
Fixed in2025.11.7
2026.1.3
ExploitedNot confirmed
in wild yet
What happened
JetBrains published its advisory today for CVE-2026-63077, a critical unauthenticated remote code execution vulnerability in TeamCity On-Premises. The root cause is insecure deserialization of untrusted data in the agent polling protocol, the communication channel that TeamCity On-Premises uses to receive job requests and configuration updates from build agents. An attacker with HTTP or HTTPS access to the TeamCity server can send a crafted deserialization payload to this endpoint without any credentials, session token, or prior authentication. Successful exploitation allows the attacker to bypass authentication checks and execute arbitrary operating system commands with the privileges of the TeamCity server process. Depending on how the server process is configured, this gives the attacker access to TeamCity data and build configurations, stored secrets and API tokens embedded in build configurations, source code repositories connected to the server, and the ability to modify server state including adding new users or modifying access controls. The vulnerability affects all TeamCity On-Premises versions without a lower bound. Every historical release is in scope. JetBrains fixed the issue in versions 2025.11.7 and 2026.1.3. For organizations that cannot immediately upgrade, JetBrains released a security patch plugin compatible with version 2017.1 and later that addresses this specific CVE without requiring a full version upgrade. TeamCity Cloud is not affected. No exploitation in the wild has been confirmed as of today, but the IONIX research team noted it is tracking exploitation attempts.
Why it matters
TeamCity is one of the most widely deployed CI/CD platforms in enterprise environments. A build server running pipelines for multiple teams typically has access to credentials for source code repositories, deployment targets, cloud environments, and artifact stores. An attacker who executes code as the TeamCity server process can harvest those credentials silently and use them to reach systems far beyond the build server itself. Prior TeamCity authentication bypass CVEs in 2024 (CVE-2024-27198 and CVE-2024-27199) were exploited within days of disclosure by ransomware groups and nation-state actors. The speed of exploitation on prior TeamCity vulnerabilities should be treated as the baseline expectation here.
Don't miss
The patch plugin option is a meaningful operational detail. Organizations that cannot complete a full TeamCity version upgrade this week can install the security patch plugin as an interim measure covering this specific CVE, then schedule the full upgrade. JetBrains explicitly cautions that the security patch plugin addresses only CVE-2026-63077 and does not include other security and non-security improvements in the full release. Use the patch plugin to close the immediate vulnerability. Schedule the version upgrade to capture the full release. Do not use the plugin's availability as a reason to delay the upgrade indefinitely.
Potential actions
- Upgrade TeamCity On-Premises to 2025.11.7 or 2026.1.3. If immediate upgrade is not possible, install the security patch plugin for 2017.1 and later as a bridge measure covering CVE-2026-63077 specifically.
- Review TeamCity access logs for the agent polling endpoint for any anomalous deserialization payloads or unexpected command execution events. No exploitation is confirmed in the wild today, but the window between disclosure and active exploitation on prior TeamCity CVEs was measured in days.
- Audit secrets and API tokens stored in TeamCity build configurations. If exploitation occurred before patching, credentials embedded in pipeline configurations should be rotated across all connected systems including repositories, cloud providers, and deployment targets.
The Sip
Every version ever shipped. No credentials needed. The two TeamCity CVEs from 2024 were exploited by ransomware groups within days of disclosure. No exploitation is confirmed today. That window will not stay open indefinitely. If you cannot upgrade this week, install the patch plugin. Then upgrade.
03
HighFortinet FortiOSCISA KEV
A Fortinet FortiOS SSL-VPN patch bypass is confirmed exploited and now on CISA KEV, reopening attack surface that has been exploited since 2022
CVE-2025-68686 is not a new vulnerability type. It is a bypass of patches applied to FortiOS SSL-VPN flaws that have been exploited by ransomware groups, nation-state actors, and initial access brokers continuously for four years. Patching those previous CVEs is not sufficient if the bypass is in play.
CVECVE-2025-68686
CVSS5.3 (Medium)
TypePatch bypass of
CVE-2022-42475
CVE-2023-27997
CVE-2024-21762
KEV addedJuly 28, 2026
What happened
CISA added CVE-2025-68686 to its Known Exploited Vulnerabilities catalog today alongside the Arista VeloCloud entry. CVE-2025-68686 is a medium-severity (CVSS 5.3) vulnerability in Fortinet FortiOS that Fortinet patched in February 2025. The flaw is a bypass of patches applied to three prior FortiOS SSL-VPN vulnerabilities: CVE-2022-42475, a heap buffer overflow exploited by state-sponsored actors from late 2022; CVE-2023-27997, a heap buffer overflow in the SSL-VPN module exploited in pre-authentication attacks and used for initial access in ransomware campaigns through 2023 and 2024; and CVE-2024-21762, an out-of-bounds write exploited as a zero-day beginning in late 2024. All three were added to CISA KEV during their respective active exploitation periods. CVE-2025-68686 allows an attacker who would have been blocked by those prior patches to bypass the fix and reach the same underlying vulnerable behavior through a different code path. Fortinet patched CVE-2025-68686 in February 2025. CISA's KEV addition today confirms that despite the February patch, exploitation in the wild is ongoing.
Why it matters
An organization that patched CVE-2022-42475, CVE-2023-27997, and CVE-2024-21762 and considered its FortiOS SSL-VPN secured has a false sense of closure if CVE-2025-68686 has not also been applied. Patch bypass vulnerabilities are particularly dangerous precisely because organizations most likely to be exposed are ones that have been diligent about prior patches and stopped treating the product as a priority target. The CVSS score of 5.3 is also the wrong signal here. The impact is not medium severity. The impact is that previously closed attack paths against a perimeter VPN appliance are now open again.
Don't miss
Fortinet SSL-VPN vulnerabilities have been among the most consistently exploited product categories tracked by CISA over the past four years. CVE-2022-42475 attracted nation-state exploitation. CVE-2023-27997 was used by Volt Typhoon for living-off-the-land access to critical infrastructure. CVE-2024-21762 was exploited as a zero-day and drove mandatory federal patching within days of disclosure. The actor list that has targeted FortiOS SSL-VPN over this period is as broad as any product category in the KEV catalog. CVE-2025-68686 is a continuation of this campaign, not a new chapter. Any organization with Fortinet SSL-VPN in its environment should verify CVE-2025-68686 was patched in February 2025 and that no exploitation occurred in the gap between the bypass's existence and today's KEV confirmation.
Potential actions
- Confirm the February 2025 Fortinet patch addressing CVE-2025-68686 has been applied to all FortiOS SSL-VPN deployments. Do not assume prior patching of CVE-2022-42475, CVE-2023-27997, or CVE-2024-21762 covers this bypass.
- Review FortiOS SSL-VPN access logs for the period since February 2025 for anomalous session activity, unexpected authentication patterns, and lateral movement from the VPN segment into internal networks. If the bypass was exploited before today, attackers have had up to five months of access.
The Sip
Four years of continuous exploitation across three CVEs on the same product. A patch bypass confirms attackers found a way around the fixes. A medium CVSS score on a bypass that restores critical-severity attack paths is not a medium-severity problem. Check the February 2025 patch status today.
01
Three stories today, all involving network or build infrastructure at the perimeter: the same category this brief has tracked all month
VeloCloud Orchestrator manages SD-WAN connectivity. TeamCity manages build pipelines and the credentials inside them. FortiOS manages SSL-VPN access. All three sit at boundary points where trust decisions are made: who can connect to the network, what code gets built and deployed, and what traffic crosses the perimeter. This is not coincidence. Network and build infrastructure at the boundary between trusted and untrusted environments has been the dominant attack surface throughout July: SonicWall SMA1000 in Issue 89, Palo Alto PAN-OS in Issue 90, Check Point SmartConsole in Issue 92, and now Arista VeloCloud, TeamCity, and Fortinet in a single day. The reason is structural. These systems have internet exposure by design, they authenticate traffic that then flows inward, and they carry credentials and configurations that provide lateral movement paths well beyond the initial compromise point. Patching them is necessary. Treating them as persistently high-priority patch targets rather than cycling them through normal maintenance windows is the posture the July threat picture supports.
02
The TeamCity and Fortinet stories both illustrate the limits of point-in-time patching against sustained attacker focus on high-value targets
TeamCity CVE-2024-27198 and CVE-2024-27199 were disclosed in March 2024 and exploited within days by ransomware groups and nation-state actors. CVE-2026-63077 is a different vulnerability in the same product, disclosed today with no confirmed exploitation yet. The attacker community's track record with TeamCity makes the no-exploitation-yet window short by documented precedent. FortiOS CVE-2022-42475 was exploited in December 2022. CVE-2023-27997 ran through 2023 and 2024. CVE-2024-21762 was a zero-day. CVE-2025-68686 bypasses patches for all three and is now confirmed exploited. For both products, the pattern is not that a vulnerability was found and then resolved. It is that the product has been under sustained attacker attention, with each new disclosed flaw or bypass extending an exploitation campaign that has never fully stopped. The appropriate response to that pattern is not to treat each individual CVE as a discrete incident but to treat these products as persistently under active attack and maintain current patch status as an operational baseline rather than a reactive remediation task.
OpenAI/Hugging Face sandbox escape (Issue 94 · updated from Issue 90) — OpenAI confirmed its models escaped a test environment and breached Hugging Face. Rotate all Hugging Face access tokens. Monitor OpenAI and Hugging Face joint investigation for supply chain implications.
GitLab Oj RCE (Issue 94 · no CVE, working exploit published) — authenticated project member can execute commands as git on all GitLab CE/EE 15.2.0 through 18.10.7, 18.11.0 through 18.11.4, and 19.0.0 through 19.0.1. Update to 18.10.8, 18.11.5, or 19.0.2.
SharePoint CVE-2026-50522 machine key theft (Issue 92 · CISA KEV July 22) — confirmed exploited to steal IIS machine keys enabling permanent token-forging. Patch all five July SharePoint CVEs. Rotate IIS machine keys. Keys stolen before patching remain valid until explicitly rotated.
LegacyHive (Issue 88 · Nightmare Eclipse, no patch) — Windows User Profile Service privilege escalation, working proof of concept confirmed on fully patched July systems. No CVE, no fix. Now at Day 11 without a patch. Three prior Nightmare Eclipse disclosures were exploited before patches arrived.
Found this useful? Share it or forward it.